Shadow folder hook script

[Leon Zandman <lz...@lode.nl>]

Hi,

This is my first e-mail to this mailing list, so greetings to you all!
At our company we've just started using Subversion two weeks ago (coming
from VSS and Sourcegear Vault) and already like it very much. We do have
one question though.

We'd like to have full (exported) copy of the latest revision of our
repositories on our server (in VSS this is called a shadow folder). We'd
like to have a plain copy of our code in case the Subversion database
gets corrupted.

As I understand Subversion doesn't come with this functionality
built-in, but you can add it yourself using a post-commit hook script.
Searching the mailing list archives and the internet I found several
scripts that offer some kind of shadow copy behaviour. They range from
simple scripts that just perform a "svn export" to advanced scripts that
incrementally add committed files (better for performance I guess).
Instead of trying them all I thought it would be wise to first ask the
people on this list if there is a script that's considered "the best" at
this moment.

We are running our Subversion server (svnserve; we'll switch to Apache
in a few weeks) on a Windows 2000 server, so the script has to be able
to run on such a server. It might be an option to install Python or
Perl, but I'd rather not install Cygwin etc.

I hope you can help us.

Greetings,

Leon Zandman


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Shadow folder hook script

[Mark Phippard <Ma...@softlanding.com>]

Leon  Zandman <lz...@lode.nl> wrote on 07/22/2005 08:39:30 AM:

> This is my first e-mail to this mailing list, so greetings to you all!
> At our company we've just started using Subversion two weeks ago (coming
> from VSS and Sourcegear Vault) and already like it very much. We do have
> one question though.
> 
> We'd like to have full (exported) copy of the latest revision of our
> repositories on our server (in VSS this is called a shadow folder). We'd
> like to have a plain copy of our code in case the Subversion database
> gets corrupted.
> 
> As I understand Subversion doesn't come with this functionality
> built-in, but you can add it yourself using a post-commit hook script.
> Searching the mailing list archives and the internet I found several
> scripts that offer some kind of shadow copy behaviour. They range from
> simple scripts that just perform a "svn export" to advanced scripts that
> incrementally add committed files (better for performance I guess).
> Instead of trying them all I thought it would be wise to first ask the
> people on this list if there is a script that's considered "the best" at
> this moment.
> 
> We are running our Subversion server (svnserve; we'll switch to Apache
> in a few weeks) on a Windows 2000 server, so the script has to be able
> to run on such a server. It might be an option to install Python or
> Perl, but I'd rather not install Cygwin etc.
> 
> I hope you can help us.

Why not just do a one time svn checkout at your mirror location.  You 
could then either just run svn update on some kind of schedule, or use a 
post-commit hook to in some way trigger the svn update as part of the 
commit.

Using a working copy makes this a lot easier since update will run 
quickly.  It doesn't sound like having the extra .svn folders mized in 
would be a problem so that is how I would do this.

Mark



_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. 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