CFUNITED Presentation - Subversion 101 plus my 2c

I was not surprised by the turnout to my "Subversion 101" presentation yesterday at CFUNITED. The amount of questions at the end of the presentation was incredible and I had to defer some advanced questions in order to get through the newbie topics.

It seems that just like going to the dentist, people know they have to do it, but choose to do it tomorrow (and recursively repeat the next day).

One issue that came up again and again was how to work with Subversion when you do not have CF server on your own machine and have to deploy a dev server in order to test code. Do you commit before you test?

My 2c is that this is really a breakdown of the development model rather than a subversion issue per se. Committing on every change does not make sense and would create a massive amount of "Garbage" revisions.
The problem of overwriting other people's code in development comes from the fact that there is only one development box. Subversion can actually help with this situation. Once both users commit their changes, those can be easily merged.

Below is the updated presentation, along with Apache configuration file code.

Click here to download the presentation