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

Re: Setting up new Subversion server

From: Ed Hillmann <ed.hillmann_at_gmail.com>
Date: Mon, 15 Jun 2009 08:10:13 +1000

On Sat, Jun 13, 2009 at 9:28 AM, Ryan
Schmidt<subversion-2009b_at_ryandesign.com> wrote:
> On Jun 12, 2009, at 15:24, David Weintraub wrote:
>> The problem with svnserve is that it can only handle a single
>> repository on a single port.
> svnserve can handle multiple repositories too, just like Apache can.
> Simply point svnserve's -r option at a directory containing multiple
> repositories instead of at a repository.

I have to agree. I've used svnserve to provide access to multiple
repositories using a single daemon, and it's behaved very well. I've
never had a problem with it. Yes, all the repositories need to be in
the same directory, but they are all completely separate repositories.
 And using svnserve is very easy.

To my mind, use svnserve if all access are intranet users (ie, users
that are inside your network). Using the httpd server is more
beneficial if you're opening your repository to the rest of the
intranet, where you want significantly more control over the access.
All our access is internal, so svnserve works a treat for us.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-15 00:11:13 CEST

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