Hello
I've just noticed a problem when using deploy:migrations (capistrano
2.5.4).
It appears that "db:migrate" is executed from the current release
directory (previously deployed), instead of the latest release
directory (current deployment).
So latest migrations shipped with latest release are not executed !
The problem occurs in migrate task (called by migrations task).
The line 374 in capistrano-2.5.4/lib/recipes/deploy/deploy.rb :
when :latest then current_release
should be :
when :latest then latest_release
So directory of the latest release (just deployed) is used to run
migrations.
I hope I'm not missing something here, and that the google group is
the right place to propose a patch...
Thanks
++
Max
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
