That solved more than the problem I posted here. Not sure why it was
doing the migrate, but right now it isn't doing the migrates either.
Brian
On Feb 23, 10:27 am, Tom Copeland <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-02-22 at 21:26 -0800, [EMAIL PROTECTED] wrote:
> > 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.
>
> > * executing "cd /home/user/public_html/staging/releases/
> > 20080223044726; rake RAILS_ENV=production db:migrate"
>
> This is only applicable for folks using multistage, but this setting
> fixes that problem for me:
>
> set(:rails_env) { "#{stage}" }
>
> Yours,
>
> tom
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
