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

Re: Using unix groups for different read/write access in a single repository

From: Haim Cohen <haimcn_at_gmail.com>
Date: 2006-12-19 20:51:46 CET

Thanks for the answers.

We're accessing the SVN using svn+ssh:// on a general purpose linux machine
without a web server.

I guess we can create a list of users periodically, but can it be based on
the unix authentication of a user (via the ssh) and without using an apache


On 12/18/06, Mark <mark@mitsein.net> wrote:
> Part of that depends on what access methods you will be supporting.
> If you are only supporting file://, then just using unix groups is
> fine. However, that is very unlikely :).
> What I would do is to set up a cronjob that runs every so often
> (hourly or less) that will build the authz file for the repository
> based upon unix group memberships. You could also tie this into your
> unix group add/change/delete process so that any unix group
> modifications are carried over into svn authz.
> On 12/17/06, Haim Cohen <haimcn@gmail.com> wrote:
> > Hi
> >
> > I would like to use single repository for several different projects.
> > I need to give a read/write permissions based on a unix group for each
> one
> > of the project and the permissions must also deny reading from other
> > projects.
> >
> > What is the way (if exist) to do such thing?
> > Should I use a different repository for every group?
> >
> > Thanks!
> > Haim
> --
> Mark
> "Blessed is he who finds happiness in his own foolishness, for he will
> always be happy."
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 19 20:52:38 2006

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.