Version control is here!

As the title suggests, version control is finally here! (somewhat)…
 
After doing a lot of research and fiddling with my website via SSH, I managed to set up a subversion repository hosted by my website. I previously tried experimenting by installing Git, but was unable to get it to compile successfully (probably due to permission issues in place on a shared hosting provider, although others on my hosting provider managed to get it working, it involved editing a lot of configurations in the config file, as well as messing with some lines in Makefile).
 
Since I’m still relatively new to subversion (but not version control as a concept), I’ve only activated it for my beta web apps that I’m working on. I didn’t want to try to set it up for my whole website, not knowing how subversion would work with wordpress and having different branches checked out and posting new updates via wordpress and having to commit them to the repository and such (or make an update with my working copy, commit it, only to have it potentially overwrite something I did in wordpress). Yeah, I could probably get around it by always doing an update before committing, but I may not always remember to do that, and frankly, wordpress is doing just fine w/ its own version control so I don’t really NEED it for my entire website.
 
With this version control system in place, I no longer need to (nor will I) make backups of the projects I’m working on by simply copying the directory somewhere else and appending “01”, “02”, etc… to the end of it.
 
Can’t wait to get back to focusing on development rather than part development, part “I better copy this in case I screw it up and can’t figure out how to get it back to the way it was”