Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Torsten van Beeck wrote: > > We have a similar web development scenario and the difference to normal > development is that it is much easier to install a compiler on each > developers box than a complete webserver. Webserver installations tend > to be done centrally. Have a test web server, with it's own sandbox, and only update the production site when you are completed. This is the only way to sanely handle large updates, since you frequently cannot incrementally change the site. We have been doing this for ages and it works really well. The key steps are these: 1) Install the test web server on the CVSNT repository machine itself 2) Checkout a sandbox for the web server (don't point the web server directly at the repository files!) 3) Set up a replication scheme to keep the web server synced to the repository Until recently, we used CVSNTUPD.exe (a little utility I wrote) to keep the sandboxes in sync (with a delay of ~ 1 minute). Now, with the massively cool postcommit option (Thanks Tony!), I have a little perl script which correctly updates the sandbox immediately. The script is not really ready for public distribution (it's very ugly), but it works fine for us. HTH John