I am having the same problem. I run 'cap staging deploy' and everything runs for the staging environment except the migrate which sets the env to production. As well I'd like to know why cap deploy does a migrate. It doesn't appear that is supposed to be part of a standard deploy.
Here is the part of the result that still uses production: ** transaction: commit * executing `deploy:migrate' * executing "ls -x /home/user/public_html/staging/ releases" servers: ["xx.xxx.xxx.xxx"] [xx.xxx.xxx.xxx] executing command command finished * executing "cd /home/user/public_html/staging/releases/ 20080223044726; rake RAILS_ENV=production db:migrate" servers: ["xx.xxx.xxx.xxx"] [xx.xxx.xxx.xxx] executing command Brian On Feb 7, 2:29 pm, drjones <[EMAIL PROTECTED]> wrote: > Hi: > I am having trouble setting remote environment variable using cap > 2.0 and multi-stage plugin. In mydeploy\qa.rb i have set > default_environment["RAILS_ENV"] = 'qa'. I have also tried setting the > envt variable in command line. > > With all of these, when I run migrations it still runs it with > production: > > * executing "cd /mnt/devint/apps/......./releases/20080207190959; > rake RAILS_ENV=production db:migrate" > > I am running cap in a windows box and attempting todeployto a unix > box. I figure I am missing some magic setting but cant seem to find > out what it is. Any pointers would be much appreciated. > > Thanks > Anand --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
