Primary DB server is where migrations are run. if deploying standard Rails stuff
I suggest making some mix-ins, and mixing them into your stages, your layout - I would expect should look something like this Capfile config/ config/deploy.rb config/stages/ config/stages/production.rb config/stages/staging.rb Anything that's universal should be in deploy.rb - stage specifics in production/staging.rb -- if one of your stages doesn't implement some behaviour, then you need to take it out of deploy.rb. There's no reason you can't add a `config/cap-load-balancer-features.rb` and load() that in your production/staging.rb files, if you don't want to duplicate code. (sorry, your last email wasn't very coherent, or I am too tired to be supporting :) - I hope my reply answered/helped - if not, post back, and I'll try again in the morning! GMT+1 ) -- Lee Hambley Twitter: @leehambley | @capistranorb -- * 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
