Re: Web Hosting using subversion

Bicking, David (HHoldings, IT) wrote:

> In fact, this is one reason I would use the following workflow for this
> project:
>
> 1. checkout code to a local workspace known by a local web server
> 2. make whatever changes are necessary.
> 3. test until blue in the face.
> 4. commit changes.

Better yet, do basic testing on this local copy and commit, then update
a dedicated QA workspace for the blue-in-the-face tests. Do not make
any changes in the QA workspace. If a test fails, fix and commit in
another working copy, then update the QA copy. This ensures that the QA
  copy can be exactly reproduced from the repository by checking out the
same revision.

> 5. backup the live site. Clear the live site.

If you strictly follow the above guideline you will always be able to
reproduce any verision you've ever run, so no need for a backup of this
state. You might want to copy the tested revisions to tags to track the
production versions.

> 6. Export the workspace to the live site.

For a less disruptive update, export somewhere and rsync the copy into
the web server(s). Depending on the changes and the web server in
question, you may need to restart the web server after the update.
Or you might rsync from the QA directory or a separate staging checkout
using the -C option of rsync to avoid taking the .svn directories.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org