On Thu, Aug 27, 2009 at 5:02 PM, Martin Eisenhardt<[email protected]> wrote: > > Hi everyone, > > I have quite a simple setup for one of my apps: one web server, one > app server, one db server. Up until now, they were all on the same > machine (node0). > > Now I want to move the db to a dedicated machine (node3). See the > deploy.rb file at pastie (http://pastie.org/596689). Now, when I run > cap deploy, capistrano tries to deploy the app also on node3, although > node3 has neither the web nor the app server role (see > http://pastie.org/596694). > > Why is that, and how do I change that? >
Capistrano will deploy to all known servers, that includes the database server. The simplest way is to just not include your database server in the configuration. Make your app server the primary database server, because that's where the migrations will be run from. If the configuration on the app server is correct at the time of the migrations being run, all should go well. No need to disturb the mighty database server with all the deployment stuff. Simple like that. It's not very intuitive, but it's the easiest way to avoid the unnecessary deployment on the database server. Cheers, Mathias -- http://paperplanes.de http://twitter.com/roidrage --~--~---------~--~----~------------~-------~--~----~ 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.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
