As far I remember, Multistage recipe doesn't automatically update your environment. You need to set it manually.
# in config/deploy/production.rb set :rails_env, "production" # in config/deploy/development.rb set :rails_env, "development" You can also set it dynamically, loading the value from current stage. set :rails_env, fetch(:stage) However, the second option requires :stage to be set before the value is assigned to :rails_env. You need to configure your deploy script or use a lambda to postpone code evaluation. -- Simone On Wed, Jun 3, 2009 at 1:51 PM, Alexey Zagarin <[email protected]> wrote: > > I have > > set :default_stage, "development" > set :stages, %w(development production) > require 'capistrano/ext/multistage' > > in my config/deploy.rb, and I have corresponding files in config/ > deploy/ for each environment. > > However, cap deploy:migrations sets RAILS_ENV=production when it runs > rake db:migrate. > > > > -- Simone Carletti Site & Blog: http://www.simonecarletti.com Email: [email protected] LinkedIn: http://linkedin.com/in/weppos Nick: weppos | Skype: weppos --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
