For what it's worth, I use SVN with isolated dev sandboxes working with trunk (or some branch). The production boxes have a webroot for staging (for detecting anything that might happen to manage to work differently in sandbox and production) and live sites. Each root is an svn copy, and there's a simple GUI to update either to a given tag in the repository.
Issac Peter Milanese wrote: > Greetings- > > I am coming up with ideas for building a new farm. We currently > run CF and Apache on a bunch of decent sized boxes, headed by a set of > F5's. We have an isolated Dev Environment. The current framework for > putting stuff into production is homegrown, and in need of an > overhaul, I just want to see if there is something out there to > assist, or if our model is wrong at this point. We do a bit over a > billion hits per annum. Now, I would like to brainstorm architectural > changes. > > Workflow as it is now: > > Developer works on dedicated dev server-> > > Developer goes to web interface in order to select items to go into > production (php/rsync) -> > > Submit process "stages" selected files (copies them into a local > heirarchy) -> > > Cron syncs that local "staging area" to the production servers. > > > > > How do larger organizations do this? > How are uploads handled? > Shared storage? > > > I think I'm just looking for other ideas. > > Any input would be great. > > Thanks > P > > ------------------------------------------------------------------------ > Yahoo! oneSearch: Finally, mobile search that gives answers > <http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC>, > not web links. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
