Re: Deployment Strategies

> As for source control, we currently use Vault. The system is set up in
> such a way that the deployed files are actually set as a working copy of
> a Vault project. After files are checked in they are updated on the live
> server by getting the latest copy. This system works ok, but I think
> there's got to be a better way. One benefit of this is that if a file
> takes down the site, it can be quickly reverted to the prior version.
> I've used Subversion on previous projects and am unsure of the relative
> merits of the two.

One feature of subversion that might be very useful is merge. If you
have multiple people working on the same code, particularly on the same
file, the changes can be merged.

Something else that might make life a little easier is to create a job
to pull out the latest version from your VCS at a known interval (eg
overnight or at 12pm and 12am). That way your updates can be regular but
people will also be aware that they need to have everything working by a
deadline.

regards
David Cameron

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com