On Sun, Feb 10, 2008 at 08:19:32PM -0700, Jamis Buck wrote: > On Feb 10, 2008, at 8:16 PM, Rick Schumeyer wrote: > >> By default, is the "deploy" task expected to run "rake db:migrate" ? >> >> Or does that only happen during the "deploy:migrate" task? >> >> If the answer is "no, deploy does not migrate db changes", then what >> is the recommended set of tasks to run when I have both code changes >> and database changes? > > cap deploy:migrations > > that will do a deploy, and run any pending migrations.
I've had the following in my config: before "deploy:start" do deploy.migrate end On a related note, what support is there for rolling back not just a deploy but migrations as well? Let's call the currently deployed version A and the older version we're rolling back to B. If I want to rollback to B I need to figure out what migration version B wants, migrate the DB to that version before changing the symlink to point to B, then change the symlink. Is that supported? > - Jamis --Greg --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
