I'm using the cap extension outlined at http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage to deploy to either staging or production environments.
The staging and production deployments are both on the same database, so when set to the same environment (in this case production), they both refer to the same database. Since it's not practical for me to have the staging release run in development mode, can anyone recommend a good way to switch the configuration to a different database? I suppose I can do it a few different ways, moving files around after code update, but I was wondering if anyone had a really neat solution. - Chris --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
