[Capistrano] Re: migrate_env behavior

[Jamis Buck]

I think what you want is the rails_env variable:

  set :rails_env, "deploy"



- Jamis

On Oct 18, 2007, at 5:27 PM, Nathan Youngman wrote:

The migrate_env variable is for setting additional environment variables that your migrations might need.

I thought migrate_env would do exactly what I wanted, which is to use
a different RAILS_ENV for the migration (2 users pointing at the same
database, but the "deploy" migration user has greater MySQL privileges
than the standard "production" user).

From reading in this group, I see that I actually need to specify:

  set :migrate_env, "RAILS_ENV=deploy"

In this case both RAILS_ENV=production and RAILS_ENV=deploy are passed
to db:migrate, though I think it will still work. Just confusing,
though I thought I'd note my concern.

Also, does anyone have any suggestions for another way of
accomplishing this?

Thanks, Nathan.


--~--~---------~--~----~------------~-------~--~----~

To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano

-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature