First, I apologize if any of the answers are obvious, I've been out of the RoR/Cap loop for a couple years, just getting back into it.
I have a situation where there is a need to deploy and manage multiple instances of the same app, potentially up to several hundred instances. Each instance requires it's own database (maybe it's own dev/production stages), but definitely at least it's own db per instance. How practical/possible will it be to manage this all through capistrano? Our older design of the app had all instances running off of one install of the code, sharing a database. For various reasons (such as the need to customize the app), this practice is no longer feasible-- as some instances will require the need to have modifications/overrides to the core code via customization plugins. Must be able to deploy new instances and upgrade current instances (as well as db migrations) Must be able to have a specific db for each instance with settings/ database.yml are created during the deployment process Ideally, the choice to have instances of a variety of different servers (we may cap it to 50 instances per server) Need to be able to run a core set of code for each instance, with customization done via plugins (that are not overwritten when we upgrade the instances via cap) So the question: is capistrano the right tool for this? If so, does anybody have any tips/recipes they could point me to for samples? Thanks in advance! -- * 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
