SVN + DAV + SSL = useful

So what if this is my first real experience with versioning systems. It's just that I really hate how CVS is layed out, how the command-line tools work, etc., and then along comes SVN that A) uses existing technology B) uses well-known technology C) rides on top of that, which gives it the benefit (in this case) of being piped over SSL, bounced around through proxies, and is in general just plain nice.

I've setup SVN, and I do plan to use it quite a bit more extensively now. I hope to get it running at school, *just* for the versioning support. However, school is windows, so that's not too likely at this rate. However, (Web)DAV is completly possible, install consists of uncommenting a line in httpd.conf and then adding a few more lines to set it up. This will allow Spencer and I to work in it from anywhere. Additionally, if I can rig up SSL for apache on windows, that'll only help it. However, DAV is a huge step up from nothing at all (due to excessive firewalling at the 'ISP' level, basically).

I actually hope to completly replace FTP with DAV soon. It runs off of apache, so I don't need another daemon running. It doesn't have a mess of firewalling crap to deal with, and clients won't have to deal with that firewalling crap. Superior? In my opinion, yes. Now, if windows shipped with a decent SVN client integrated into explorer, THAT would make things nice.

So now, it's just a matter of setting up my server with DAV correctly. I figure root path point to /srv/sites. Anyone can access their site via DAV @ https://dav.brantleyonline.com/(domainname), with the corresponding credientials. Of course, there's only one letter of difference between "dav" and "dev", and as they'll both be subdomains....eek. Typos are going to suck royally, and I fully expect to make so many stupid mistakes it'll scare me.