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

RE: Re: Strategies for projects/branches layout

From: Miha Vitorovic <mvitorovic_at_nil.si>
Date: 2005-11-08 08:45:55 CET

"Jesse Erlbaum" <jesse@erlbaum.net> wrote on 07.11.2005 21:09:10:

> > The disadvantage is you can't enumerate all repositories on a server,
> > only directories within a repository. So that makes it a little more
> > awkward, but I think the benefits far outweigh.
>
>
> Problem with this is redundancy, particularly if I want to assert that
> all the "modules" in a repository are accessed by the same group of
> people. For example
>
> Repository: "CLIENT_A"
> Modules: "PROJ_1", "PROJ_2", "PROJ_3", "PROJ_4", "PROJ_5"
>
> This way I can set UNIX permission such that all users who work with
> Client A have access to all the projects.

Why use UNIX permissions? Apache SVN WebDAV module has built-in
authorization which supports groups, so you can control access to all your
respositories from one file. And in 1.3 svnserve is getting this too.

Cheers,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 8 08:48:06 2005

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.