secure svn configuration

[Heston James - Cold Beans <he...@coldbeans.co.uk>]

Good afternoon guys,

 

I've been using SVN for a fair while from a general user perspective,
checking out and committing code to and from various repositories, however,
I've now been tasked with taking on the admin duties and configuring a
subversion server.

 

I wanted to get your advice on how best to do this so thought I would
explain a little about my server setup and our requirements as a development
team in the hope you'll point me in the right direction.

 

We have a dedicated Windows 2003 server running IIS with a single public
facing IP address. We have maybe 4 or 5 developers which will be accessing
the projects hosted on the server. Are we able to configure multiple repos
on the single IP? I would imagine so, I just can't quite see how. I'm
imaging something like:

 

Svn://svn.mydomain.com/project1

Svn://svn.mydomain.com/project2

Svn://svn.mydomain.com/project3

 

As we're using IIS as our core web server for our sites I've been looking to
using the 1-click-svn solution to get subversion running on our server, is
this my best option? 

 

We will have multiple projects on the server, none of which are related, am
I best having these as separate repositories? Or as a single repo with a
project tree within it? I've read that having separate repos is the best
option if the projects are unrelated and you want separate version numbers
for each, but I really don't know.

 

We need to secure the repos with a username and a password as the
information contained within them is quite sensitive, how is this best done?

 

I really appreciate your advice on getting this up and running guys, I'm
excited to see how subversion works from an admin point of view.

 

Cheers,

 

Heston James