RE: Updating a live website with a post-commit hook script

On Thu, 2006-06-29 at 11:53 -0400, jason@subversus.org wrote:
> You've asked the question and gotten several responses saying that you
> either can't do what you want, or that what you want to do can be done much
> easier by simply using post-commit hooks to update a working copy that can
> be served by Apache. Yet you keep arguing.
>
> If you think all of those responses are wrong, wouldn't it be easier to go
> and try it out and if those responses were proved incorrect (unlikely) to
> provide this new-found knowledge back to the mailing list?

Slight variation on the question: how would you make the site stay
at a tagged version so untested changes could be committed, then
tested and tagged when verified? I used to do this with CVS by
rtagging the tested copy to float a known tag to that version, followed
by an update to the working version, always using the same tag. That
way it didn't matter if additional untested changes had been committed.
The script also floated a couple of previous-release tags backwards
so you could always back out to earlier versions without having to
track any release numbers or tags.

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