We aren't doing this multiserver yet, but it was certainly considered when we wrote all the scripts.
We essentially have a single SVN server which we upload and tag all our code to come release time. On either our dev or prod server we hit a script, which pulls in all the code from SVN into a new directory, runs build all and cc the cache (not strictly necessary as it should be blank), it then creates a single symlink to point to the new directory leaving the old code base in an old dir (so we can switch back quickly when things don't work out as planned, not happened yet...). We just keep the last copy of the code on the server and the current one, old ones are deleted off the servers. This gives us little if no down time, just the amount of time it takes to recreate a symlink, but again this is all scripted. So for taking this multiserver we just planned to split the scipt in two, the prepare from SVN and symlink scripts, then execute these using clusterssh, so in theory is should all come up nicely in one go, at least thats the plan. Oh some further points of interest, the scripts written automatically produce config.php and the main controller file as these different between our servers (prod and dev, and the developers windows machines). Dont know if this is "the" way to do it, but certainly works well for us, makes it very easy to roll out our new versions, all you have to do it tag a release(also scripted on the dev server), then execute the scripts. Hope this helps, Mat -----Original Message----- From: Pete Connolly [mailto:[EMAIL PROTECTED] Sent: 22 November 2007 19:00 To: [email protected] Subject: [symfony-users] Re: best practices for a symfony roll out On Thursday 22 November 2007 17:29:06 Wang David wrote: > What's the best practice for rolling out a symfony release on a > multiple server environment? > > On the base server ive written a script that called symfony to rsync > to each server. > > After its been deployed to each server i execute a shell script on > each box that brings the server down and then clear-cache and fix- > perms then ups the server again. > > Can other ppl talk about how their multiserver deployments are done.. > > (happy thanksgiving to our US guys!) > I've yet to deploy an release onto more than a single server, but from past experience with multi server rollouts, clusterssh is a very useful tool. http://clusterssh.wiki.sourceforge.net/Main+Page Have a look, it might speed things up for you. Cheers Pete --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
