Jeremy, You'll have to re-architect your system to include the stage in the :deploy_to, this is a smart move anyway, (personally I use /opt/sites/:application/:environment) - then simply add the staging server as a normal server in the production deployment.
You could take it a step further and set some additional options on the server (staging) that it can be excluded from spinning up web servers/etc - Lee On Monday, June 4, 2012 at 11:50 AM, Jérémy Lecour wrote: > Hi, > > I use a multistage Capistrano configuration. I have 2 serveurs 1 for > production and 1 for staging, and there are 2 stages for capistrano, with the > same configuration (deploy_to, …) That way, my production and staging > environments are very similar. > > Having just 1 production server, I'd like to be able to switch to the 2nd > server in case of emergency, or for a scheduled long maintenance. > My staging server is perfect for this, but I don't want to use the staging > DB, app, … for the production environment. > > I 'd like to tweak my production deployment strategy to mirror every > deployment to the 2nd server but with a specific configuration (mainly the > "deploy_to" variable). > > Is there a way to do that? > > Thanks for your help > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > (mailto:[email protected]) > * To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]) For more options, visit this > group at http://groups.google.com/group/capistrano?hl=en -- * 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
