Thomas Harold wrote:
>
> The big issue (in my mind) of having 100s of repositories is that it
> becomes a large administration headache (well, until you manage to
> script everything). It can be more complex for the users as well.
I am using mod_dav_svn as a front end, and the SVN authz file is
automatically configured from a database, so I just as well script 100
<Location> directives into the httpd.conf file, as I can script the
entries for repository paths in the SVN config file.
However I am wondering whether there are any consequences for apache
having 100 or more sets of Location directives;
<Location /siteA>
DAV svn
SVNPath /usr/local/svn/siteA
# our access control policy
AuthzSVNAccessFile /path/to/access/file
</Location>
<Location /siteB>
DAV svn
SVNPath /usr/local/svn/siteB
# our access control policy
AuthzSVNAccessFile /path/to/access/file
</Location>
I can easily script the files for such a configuration, so I will do that and report back...
>
> We put our repository databases on a separate partition (ext3). Which
> will give us the flexibility of tuning the file system.
It looks like the requirement is to put the repository files on an NFS
mounted filesystem.
Thanks for your suggestions,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 28 16:56:39 2006