We use two methods here, one method pushes updates via a hook script
(for local updates), the other method is a cron job that runs every
couple of hours and issues the svn update command. If you want immediacy
then may I suggest using a hook script which pushes the updates to your
site when your production branch is updated.
//C
-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com]
Sent: Wednesday, May 17, 2006 5:53 PM
To: Jamie
Cc: users@subversion.tigris.org
Subject: Re: automatic deployment or websites
Jamie <jam5t3r@gmail.com> wrote on 05/17/2006 08:48:34 PM:
> What tools are available for monitoring a repository and updating a
> production server when the repository has changed?
> I'm looking for the most simple solution with the least overhead, I'm
> already worried about the server not being able to handle the load but
> the client does not want to pay for 2 servers.
The easiest thing to do is to use svn checkout to turn your web site
into a normal working copy. Then you just need to run the svn update
command to deploy changes. In most cases, you could just run a process
once a night, or every hour, that runs the svn update command. If there
are updates, they will be pulled down.
Mark
________________________________________________________________________
_____
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM
Email Security Management Services powered by MessageLabs.
________________________________________________________________________
_____
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 18 17:53:55 2006