Capistrano would be a great tool for this job. You'll put all your common config in config/deploy.rb and then include only the variations (paths, dbnames, etc) config/deploy/*.rb
It's dry and you can compose 'one task to deploy them all' that simple calls the others if required. - Mike On Thu, Nov 4, 2010 at 12:17 AM, Charles Calvert < [email protected]> wrote: > Problem: > > I have a number of Joomla installations that I need to manage. I was > looking to use Capistrano to automate the deployment of updates. This > involves: > > 1. Taring up the files and then copying the tarball to another location. > > 2. Using mysqldump to export the database, compress it and copy the > compressed file to another location. > > 3. Copying the compressed tarball containing the updates to the server, > uncompressing and untaring it to the appropriate location. > > On top of that, I have two different types of servers and accounts to > work with: > > A. A shared web hosting account. The paths are the same for all > accounts, but the ssh credentials, database credentials and database > names are all different. I can't change that. I was going to deal with > the database stuff by extracting it from Joomla's configuration.php, but > the ssh credentials can't be unified. > > B. Multiple installations on a single host, each in its own path. I > would use the same ssh credentials, but the paths all vary. The > database names and credentials do too, but again can be extracted from > Joomla's configuration.php. > > I've been reading past threads, including this one: > < > http://groups.google.com/group/capistrano/browse_frm/thread/cba0d3817621a55d/4103e04af7c64fb4 > >. > > Using local scripts to handle the variance on the server would work for > the paths on server B, but strikes me as an inelegant work-around. Why > replicate something on the remote server that could be, at least in > theory, handled as a task in the local Capistrano recipe? > > From everything I've been reading, it looks like Capistrano is really > intended to perform the exact same task on a bunch of servers that have > identical paths, identical resource names (e.g. databases) and identical > authentication credentials. This makes a lot of sense if your use case > is the standard development -> staging -> production deployment. In > this particular case I'm doing something different. Am I using the > wrong tool for the job? > > Thanks, > > -- > Charles Calvert > Celtic Wolf, Inc. > (703) 580-0210 > [email protected] > http://www.celticwolf.com/ > Blog: http://www.celticwolf.com/blog/ > Twitter: celticwolfinc > > -- > * 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]<capistrano%[email protected]>For > more options, visit this group at > http://groups.google.com/group/capistrano?hl=en > -- *Mike Bailey* *Mobile: 0421 806 002* PO Box 2016 Fitzroy VIC 3065 [email protected] www.goodfordogs.org -- * 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
