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

Re: How to "stage" input from a broad community?

From: Matt England <mengland_at_mengland.net>
Date: 2006-02-08 20:58:59 CET

At 2/8/2006 11:25 AM, Frank Gruman wrote:
>Absolutely - it does. Check out the Subversion Book :
>That should give you a start of an idea on how to manage that. You can
>grant read, write, or both access to remote users to any directory within
>a repository.

Ok, great.

Unfortunately for me, this access-control stuff apparently requires an
Apache integration on the svn server system, something I have tried to avoid.

My general nature is to avoid inter-system dependencies if I can. eg, one
benefit of this: my Apache has gone down occasionally for maintenance,
crash, etc...but my subversion repos are still merrily chugging along
because svnserve doesn't care what Apache does. It's a nice, minimal
system. I don't muck up my Apache config with subversion stuff,
either. Alas, it (svnserve) doesn't have ACL features...or apparently
so...so maybe I'll just run a separate Apache server from the main web site
if I want my independence.

At 2/8/2006 11:24 AM, Kevin P. Fleming wrote:
>Have you read the Subversion book? It clearly documents how to do
>path-based access control.

I don't see any documentation for an svnserve-based access control...nor do
I know how this would be controlled given that svnserve implements access
control via ssh...and I see easy way for ssh/unix-login-based access
control mechanisms to be plugged into svnserve.

Alas, as Kevin mentions, I don't read the svn book from cover to cover,
hence I hope to find help for point problems here, for which I've very


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 21:01:58 2006

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