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

RE: Pratical SVN

From: Rob van Oostrum <rob.vanoostrum_at_blastradius.com>
Date: 2005-07-21 03:52:49 CEST

http://svn.collab.net/repos/svn/tags/1.2.1/tools/hook-scripts/

Look at svnperms.py and svnperms.conf.example. It'll let you define paths with regular expressions (wildcards on steroids). You call the Python script from the pre-commit hook script of your repository.

Again, for the changing passwords, you might want to consider leveraging the MS Active Directory you probably already have anyway. See my earlier email for more on that.

Cheers
Rob

-----Original Message-----
From: Calvin [mailto:szguoxz@hotmail.com]
Sent: Wed 7/20/2005 6:44 PM
To: users@subversion.tigris.org
Subject: Pratical SVN
 
Hopefully this is my last question. :-)

I get pretty everything figure out except the security (this was my concern
from the beginning.)

Using Apache, auth_svn_mod, could give me per directory access control, but
I still need the following 2 features:

1. I have to allow developers to change their own password.
2. I have control the access at dir/file level based on wildcard match.

        Here is the scenario:
        I want to make sure no files under bin folder can be checkin in the
whole solution:

        So I need some kindof (like nant):

        [/**/bin/**]
        * =

        I also want to make sure only admin can change my build scripts. So
it will be:

        [/**/*.build]
        @admins = rw
        * =
        
        When I say "*" here, I mean everybody, not anonymous use.

        Is there anyway in SVN in accomplish this?

        Thanks,

        Calvin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 21 03:57:56 2005

This is an archived mail posted to the Subversion Users mailing list.