I’ve been thinking of other ways to put my Windows Home Server to good use and my recent trip to Florida got me exploring ways I could work on a couple of personal coding projects while traveling. Eventually much of this code may well get published on CodePlex but for now it’s very incomplete and I need somewhere to work on it.
I’ve been using Subversion for a while. It’s small and simple enough to run on my development machine at home to give me source code control on small personal coding projects (read more about the development tools I use). I needed to expose a server so I could access it remotely. Windows Home Server already supports this, all I had to do was get Subversion running on it.
I ended up installing Subversion on my Home Server box using the VisualSVN Server installer. VisualSVN Server has a nice setup that installs the Apache web server and Subversion. The downside of this is I now have two web servers running on my Home Server box but the low friction install makes up for that at the moment.
Some notes on the setup:
- Overall the install process is very similar to installing the Squeezebox software I up on WHS last month.
- Remember to install everything into a \Program Files\ folder on the D: drive and not into the WHS system drive, which is very small and will quickly fill up.
- I created a D:\Repositories folder to store my Subversion repositories. The other alternative is to create a folder under D:\Shared but to turn off duplication for that folder, otherwise you’ll get file locking issues (according to this post).
- Assuming you already have your WHS setup to share folders and allow remote access all you have to do is reconfigure your firewall(s) to open a port for Subversion. By default this will be 8443.
You should now be able to open https://myserver.homeserver.com:8443/svn/ in a web browser and see you repository you created.
VisualSVN also makes a VS client plug-in which I’m considering taking a look at although it’s $49 a seat.
Update 1st Dec: A friend here at Microsoft just pinged me to say they’ve set something similar up using Visual Studio Team Foundation Server 2008. I’ll probably be adding another blog post on how to set this up.