On 12/12/06, Jared Hardy <jaredhardy@gmail.com> wrote:
> On 12/11/06, Rob van Oostrum <rob.vanoostrum@blastradius.com> wrote:
> [snip]
> > I did a prototype a little while ago
> > using one writable repository with any number of read-only mirrors
> > that would reverse-proxy any attempt to write to the repository to
> > the single back-end writable repository. This seemed to work just
> > fine, and it gives you the single point of transactional scope needed
> > to prevent conflicts and collisions in the absence of a distributed
> > transaction capability. I used rsync to run the synchronization back
> > to the mirrors, but there's no reason why svnsync couldn't come in
> > handy here.
> [snip]
>
> How did you implement the reverse-proxy? I have been looking for a
> solutions for multi-homing the svn repository, for read-only type
> operations (update) via svnsync, and using a reverse-proxy for write
> operations (commit).
This functionality has just been committed to Subversion trunk and is
being tested for production by one of our committers in his company
environment. It will be part of 1.5, but you can benefit from it
earlier if you build and use our trunk code.
You will need Apache 2.2, APR 1.2.8 (newest release) and Subversion
trunk (aka 1.5-dev). See recent posts to the dev archive:
http://svn.haxx.se/dev/archive-2006-12/0126.shtml
and see
http://svn.collab.net/repos/svn/trunk/notes/webdav-proxy
for configuration.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 12 12:17:46 2006