I have no experience with deploying to multiple servers, but it's clear even to me that you should run disable app before you run rsync. So I suggest this scheme: 1) server1 disable app, server 2 disable app, etc. 2) rsync to server1, server2, etc 3) run migrations if any 4) server1 enable app, server 2 enable app, etc. (clear-cache is included into enable app if any). Also if you have many servers, it's probably better to execute your pre-deploying/post-deploying scripts remotely (via ssh) from your base server. I use this for single server as well, when deploying using eclipse + apache ant + symfony sync + ... So deploying takes one click and 20 seconds of me.
Also consider that even if you disable app, there can be some slow scripts still running and possibly including files already changed by rsync, and therefore break. Good luck. 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!) > > -d > > > > > -- -------------------------- With best regards, Wicked. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
