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

Re: Where to locate repos (on Linux)

From: Noah Spurrier <noah_at_noah.org>
Date: 2007-11-03 02:15:43 CET

On 2007-11-02 13:28-0700, Micah Elliott wrote:
>I've been putting repos in various places, and I'd like to hear
>if some of those places are more popular or more standard than
>others. I can't figure out from FHS
> ...
>I tend to use /var since it's deemed "variable", or changing
>data. The book (svnbook.org) uses /usr/local/svn, which sounds
>reasonable, but slightly in violation of FHS, since a repo is
>really "variable" data. So maybe /var/local/svn is best?
>I'd like to standardize on something going forward. What is your

I put it under:


I simply use `adduser` to create an svn user and group. I put each developer
in the svn group. As the svn user I use "svnadmin create /home/svn/src" to
initialize the "src" repository. Then I do `chmod -R g+w /home/srv/src` on
the repository directory. I don't know if this is the best way to do it, but
it's easy. I don't think it is correct to give group write to all of the
repository because then idle hands could modify the conf or hooks directory,
but we have a small group, so it's "OK" for the time being. I was actually
planning to write this mailing list to ask what is the best way to setup
group access to the repository. In our group we use svn+ssh for connecting to
the repository. I like this setup because it's easy to manage the access. I
just have to add them to the svn group.

I don't like /usr/local/svn for the repository data. /var/svn sounds a little
better, but I'm sticking with /home/svn until somebody tells me why that's

  Noah Spurrier | email: noah_at_noah.org | http://www.noah.org/wiki/engineering 
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 3 02:16:17 2007

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.