Alexey,
That is the default behavior, you may have to try setting a variable called
:migrate_env, and see what difference that makes, you may have to to set it
with a lambda, something like this:
set(:migrate_env, { stage })
That should not err if stage isn't defined (something you may run into a few
times with multistage) -- only evaluates the {} when the variable is
accessed.
The actual task definition, is here in the code:
http://bit.ly/MTSFP
- Hope that helps
2009/6/3 Alexey Zagarin <zaga...@gmail.com>
>
> 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.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Capistrano" group.
To post to this group, send email to capistrano@googlegroups.com
To unsubscribe from this group, send email to
capistrano+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.co.uk/group/capistrano?hl=en
-~----------~----~----~----~------~----~------~--~---
