Thanks for the great details. I think I shouldn't mess with the way our application is deployed to all 3 servers, from what I understand it can create some major issues during a roll-back.
For the migration: If I set migrate_target to :latest then this will work OK when my deployment wasnt a success and a roll-back happened. When the deployment is successful the symlink points "current" to the "latest release", if not a roll-back happens and symlink points to the previous latest_release. So if I set target to latest does that mean it will still update the database even though code update wasnot successful and symlink was not performed? I think I am confusing myself! Is there a difference between cap deploy migrate vs cap deploy_with_migrations? This can be analyzed for 2 cases: migrate_target=current or migrate_target=latest. thanks --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
