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

Re: Shared repo location on server?

From: Rush Manbert <rush_at_manbert.com>
Date: Thu, 07 Feb 2008 18:00:26 -0800

Kevin Grover wrote:
> On Feb 7, 2008 12:28 PM, Rush Manbert <rush_at_manbert.com> wrote:
>
>
>>Here's a dumb question. I have a large repository that will be shared by
>>multiple developers. We're hosting it on a Mac running OS X, so it's a
>>Unix box. Where do people normally locate the repository directory in
>>this situation?
>>
>>I originally created the repo on my local system, and I put it in
>>/usr/local/share/companyName/svnRepos/specificRepositoryName, but I
>>suspect that's not a good "official" location.
>>
>>
>
> There's no one correct answer. However, you're safer if you keep the
> repository somewhere where people can't write to it (directly) and let
> svnserve or Apache handle access to it. This also prevents problems of one
> person accessing it with a 'newer' version of the client and silently
> updating something in the repository (because file:// protocol repos get
> accessed directly by the client).
>
> In Linux (or other Unix boxes), I created an svn user account. In svn's
> home directory, I created a directory called 'repos' and put my repositories
> in there. I set up a svnserve service that gets run (as user svn). I also
> put scripts to back things up in ~/bin and have them run automatically by
> cron (scheduled) jobs.
>
> You could probably do something similar in on a Mac.
>

Thanks Kevin. After reading The Book some more and seeing what I could
do with public/private key access through a single account, I did
exactly what you suggested.

- Rush

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-08 03:00:51 CET

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.