This is exactly what I want.
Using SVNPath it works very well, except I must restart the server
every time I create a new repository.
On 12/8/05, Branko Čibej <email@example.com> wrote:
> Ben Collins-Sussman wrote:
> > Hm, that seems like pretty unusual use-case. Admins are the ones who
> > typically manage authz policy files, not arbitrary groups of users.
> Yes. The devil lies in the definition of "admin" -- specifically,
> "server admin" vs. "repository admin".
> At work, I created a similar setup (without the SVNParentPath) -- the
> server admin can create repositories, but the repository admin can edit
> the mod_dav_svn authz.conf file, which is stored in the repository
> itself. That way, project managers can add or remove peoples' access to
> the project's repository without having to bug the IT department -- or,
> worse yet, me! :)
> -- Brane
Received on Thu Dec 8 14:56:18 2005