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

Authorization schema per repository

From: Hernan Desio <HDesio_at_Technisource.com>
Date: Sat, 30 Aug 2008 12:47:20 -0400

To whom it may concern
 
    We are migrating our svn structure from svnserver to Apache, and we
found something that we do know if is possible to do or not under Apache.
First a brief introduction of our business. We are an outsource company,
that works with many clients, and several projects for each one. For this
reason obviously we have to maintain confidenciality between repositories.
Actually the svnserver is pointing to a "svn" folder in our server with the
structure under the svn folder as follow:
 
svn/
    Client 1/
        Project 1a <-- Repository
        Project 1b <-- Repository
        Project 1c <-- Repository
 
    Client 2/
        Project 2a <-- Repository
        . . .
        Project 2n <-- Repository
 
    Client x/
 
And each Project folder is the repository for the project.
 
With svnserver, each project can assign independently of others the user and
authorization schemas, and that is great beacuse each PM can control the
persons working in each project without accessing (or messing) with the
rest. This is possible because svnserve searches for the autorization file
under each individual repository.
All the documentation I read so far for Apache, indicates that to provide
authorization per repository / folder I have to add the
 
    AuthzSVNAccessFile C:\svn\authorization.conf

and in it create 1 entry per repository and / or tree
 
 
My question is simple. Is there a way that apache searches for the
authorization file under each individual repository, instead of haveing a
global file? (obviously without having to change the httpd.conf everytime we
add a client or create a new repository?
 
I'd appreciate any comment.
 
Thanks
 
 
 
Received on 2008-08-30 19:13:19 CEST

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