[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Single Server, Multiple Repositories, Multiple Locations

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Mon, 03 Mar 2008 10:15:36 -0500

VirGin wrote:
> Currently I have one repository that has several different projects. I
> access the repository via svn:. SVN is running on one machine and the
> repository is stored on another.

This is not a good idea, just to start with. Whether you are using
svnserve or apache, it is best to have the server process local to the
repository files. The reason for this is that remote filesystems do not
(as a rule) support the kind simultaneous access and file locking that
Subversion requires. You may be able to get away with it if you have a
very good NFS implementation, but it can lead to repository corruption.

> I would like to create multiple repositories on multiple machines but
> access all of them via one server.

It's not possible with the current code, and for the reasons above,
isn't likely to be added either.

Is there some reason you can't host all of your repositories on a single
box? Or some reason you can't run multiple servers (one per
repository)? If you are trying to maintain a central authorization
structure for all of the repositories, there are any number of ways to
accomplish that and still have independent repositories: one of the
easiest of which is to have another repository contain the ./conf
directory itself and use a post-commit update all instances.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-03 17:19:00 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.