Re: a few nits setting up svn...

Ben Collins-Sussman wrote:

>On Thu, 2004-02-12 at 16:24, Perry E. Metzger wrote:
>
>
>>4) As an aside, it would be neat if one could make the ra_svn goo
>> operate suid "svn" or something similar, so that the repository
>> could be writable only to "svn" and accidents could be avoided.
>>
>>
>Why don't you make the whole repository owned by user 'svn', then run
>'svnserve' as a daemon, running as user 'svn'? That way, only one
>process will ever access the repository, and you don't need to worry
>about group perms or umasks or any other permissions accidents. Very
>clean and simple.
>
>

I was thinking the same. IMO, directly accessing the files via file:
method and svn+ssh: is a really bad idea unless there's only 1 person
using it (ie, personal projects). The Unix permission scheme just isn't
cut out for robust multi-user sharing like what needs to be done with svn.

Go with apache/mod_svn or svnserve for large projects.

-- 
Brian Mathis
http://directedge.com/b/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org