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

RE: Controlling update and/or commit access to a repository URL

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-09-03 22:38:36 CEST

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:41:08 2004

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.