svnserve pointing at a NFS share = BAD there will be people who say that
you can mount a repo on NFS shares, but its a very bad idea because it blows
up in unexpected and subtle ways
a better way is to have a master server and then use slave servers and
svnsync. the slaves will only be able to do checkouts, but I have a feeling
that doesnt matter in your case
if you want to be able to track who did what, you need some kind of
authentication, even if they have empty passwords; otherwise you will get
anonymous commits on everything
On 5/7/07, David Ferguson <firstname.lastname@example.org> wrote:
> Could you guys take a look at my plan for setting up a Subversion server
> farm and let me know if you see any gotchas?
> 1. There will be six machines running svnserve, all pointing to the same
> root (-r option). This root will be an NFS mount of a directory that
> contains the many repositories for the projects that this farm must serve.
> 2. Each machine will have a unique name in DNS like svn1.mydomain.com,
> svn2.mydomain.com, etc. but will always be accessed by clients through
> svn.mydomain.com. To provide some load balancing, svn.mydomain.com will
> be an alias that will map to specific svnX.mydomain.com servers in a
> round-robin fashion.
> 3. No authentication will be done (this is all behind the company firewall
> and all users are trusted)
> 4. All repositories are using FSFS.
> See any issues? I am most interested in this: Is it okay to have
> multiple machines running svnserve, possibly accessing the same repository
> at the same time? From all I read it is, but I just wanted to be sure.
> thanks in advance,
Received on Mon May 7 22:57:55 2007