cool....
thanks for the update... but i have a question.. how does one run multiple
versions of the httpd process simultaneously on the same server...????
this would definitely solve my issue!!!!!!
i'm asusming that the external 'dat' file that you state is reparsed on
every http connection is easily structured in a manner that allows me to
specify a given repository directory, and to specify the user/group that has
access to that given directory. i do have one question though regarding the
file that you specify. is it a standard text file, that contains
user:password pairs, and is the password plain text, or is the password
encrypted (md5)....
thanks...
-bruce
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Friday, September 03, 2004 1:39 PM
To: bedouglas@earthlink.net
Cc: 'Lee Merrill'; users@subversion.tigris.org
Subject: RE: Controlling update and/or commit access to a repository URL
On Fri, 2004-09-03 at 15:32, bruce wrote:
> if you want to restrict a user from being
> able to access a given directory within a repository, the only way you can
> really do this through svn is via the apache setup.
Correct, you must use apache.
> the issue with this is
> that if you want to dynamically modify the users, and the given
> dirs/permissions that the users will have with respect to the dirs, you're
> going to have to modify the httpd.conf file on a continual basis, which is
> going to require restarting the apache server....
Incorrect. Use mod_authz_svn. Read chapter 6. It's exactly for this
purpose: controlling read/write access to specific directories by
specific users and groups. No apache restarts required. Everything is
defined in a single file that is re-parsed on every new HTTP connection.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 3 22:52:18 2004