[wellylug] SVN: svnserve vs apache?

[John C Barstow]

On Thu, 2007-07-12 at 10:22 +1200, Sigurd Magnusson wrote:
> SilverStripe
> I've asked a bunch of questions on how we should make the
> SilverStripe 
> code open via SVN, and not just our dailybuilds...
> Those with SVN experience could you please provide insight? :)
> 

I've set up a couple dozen repositories, so I think I have some
experience here.

The typical setup is to offer read-only access over HTTP and commit
access over svn+ssh. This works really well for a couple of reasons.

For random individuals, http access is much more firewall friendly.
Third-party tools invariably support HTTP (because it's easy). It's very
easy to set up an svk, git-svn or bzr instance that tracks your HTTP
interface. In addition, you can browse the source with your web browser
- essential for turning casual interest into active contribution.

For write access with a small number of committers, svn+ssh is easy to
administer and very secure, especially if you use key-based security.

Write access via http is better for intranets, where Apache can delegate
the authentication portion to your LDAP/Active Directory server.  Then
you only need to maintain the authz file.

John C Barstow