Greetings,
We're setting up an enterprise svn server, running via Apache on
RHEL3. This will host multiple repositories for multiple development
groups. What I'm trying to figure out is:
Can multiple access control files be set up under one Location
directive and SVNParentPath, or is the only way (if I want more than one
AuthzSVNAccessFile) to have each repository in a distinct Location
block?
This server will have 100+ users at the beginning, and I would like to
delegate some of the user list maintenance to the repository admins. My
wish would be to be able to do something like this in the default access
file:
[repos1:/]
<include file-x>
or to have multiple AuthzSVNAccessFile directives in the Location
block. I love the ability of SVNParentPath to set options for all the
repositories, but I don't see how to allow repository admins to maintain
their lists without giving them the ability to corrupt the access
configurations for all the repositories in the system.
Currently, I've got this in httpd.conf:
<Location /svn>
DAV svn
SVNParentPath /svndata/repos
AuthType Basic
AuthName "Subversion TEST Repository"
Satisfy Any
Require valid-user
AuthzSVNAccessFile /svndata/svnconfig/default-access-file
SVNIndexXSLT "/svnindex.xsl"
SSLRequireSSL
ErrorDocument 403 /403error.html
</Location>
(403 ErrorDoc because the RewriteEngine / RewriteRule doesn't seem to
work for some reason . . . )
And default-access-file:
[/]
* = r
[repos1:/]
* =
user1 = rw
user2 = r
etc.
Any thoughts appreciated. Thanks!
--Cedric Williams
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 11 18:10:20 2005