I've finally managed to get my server up and running with
mongrel_cluster and all that jazz. My rails app works fine, but when I
try to access my svn repos as I was doing before everything was setup
rail is giving me a 404.
I usually find it easier to create a separate subdomain for Subversion, say svn.example.com. Then you can have a separate virtualhost for your repository and won't have to fiddle too much with Apache routing.
I've finally managed to get my server up and running with
mongrel_cluster and all that jazz. My rails app works fine, but when I
try to access my svn repos as I was doing before everything was setup
rail is giving me a 404.
I usually find it easier to create a separate subdomain for Subversion,
say svn.example.com. Then you can have a separate virtualhost for your
repository and won't have to fiddle too much with Apache routing.
> I don't suppose you have an example of how I would do this. I'm not very
good with server type stuff.
You will need to setup the subdomain in DNS. Then you will need to restore your previous virtualhost config (the one where svn was working). Keep your current virtualhost (the one where your Rails app is working) and add the svn one so you have two separate virtualhosts.
My virtualhost for svn looks like this (except I changed the domain):
SVNParentPath assumes that repositories are in subdirectories to this path. If you only have one repository you shouldn't use SVNParentPath, I don't recall the right directive, check the docs.