RE: Web development development process

What's wrong with using working copies for production? We did configure
apache
to reject any request with .svn in the url.

It means that my deployment vehicle is a simple 'svn co' or 'svn
switch'. No
messing around with packaging up the files, etc. And this really comes
in
handy when an update goes bad and I need to revert quick. Plus all I
have to
do to release to QA is give them the branch and revision.

I can check that nobody has messed with anything on the
production server with a simple 'svn status'. And I can revert
any such change (or commit it if I made it :) )

I even have /etc under svn now :) Makes it very easy to deploy new
servers.
I request a new hardware unit and the hosting company installs the OS. I

install some ssh keys and install/update a handful of packages, do a
couple
svn co's and update public DNS and I'm up and running.

JLM
Jeremy L. Mordkoff
Received on 2010-09-15 16:15:22 CEST