Lee,
Thanks for the reply!
I added the following line to my deploy.rb and tried again:
before("deploy:migrate") { reset! :releases }
Before the svn checkout, the current release was 20100215213658 ...
the svn checkout created 20100215214424.
It goes through the whole update_code, etc. and then comes to
deploy:migrate... where I see the following:
* executing 'deploy:migrate'
triggering before callbacks for 'deploy:migrate' (<-- I'm assuming
this is my reset call)
latest => /path/to/my/app/releases/20100215213658
* executing "cd /path/to/my/app/releases/20100215213658; rake
RAILS_ENV=production db:migrate"
It's still executing against the old release even though I reset
the :releases variable.
Am I missing something?
On Feb 15, 2:24 pm, Lee Hambley <[email protected]> wrote:
> jmadtech, sorry for the late reply - I had thought of that, but couldn't
> find the thread before work this morning to refer you to.
>
> Please, come back to us - and no apologies required, that's one of the most
> comprehensive `problem` reports we've had on here in a while, it's great to
> see that you really grok the deploy process.
>
> -- Lee Hambley
>
> Twitter: @leehambley | @capistranorb
--
* 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.com/group/capistrano?hl=en
