Having version control is one of the sound practices of a good programmer.  Version control can be done manually, but is quickly a very administrative and error-prone task, so many development organisations try to use automated systems, such as Microsoft’s Visual SourceSafe or other applications. There are also open-source counterparts, such as the old and trusty CVS, or the newer Subversion.
What is interesting, however, is that many system administrators and architects do development too, but without any  version control.  A set of scripts is not as elaborate as an accounting application, but without proper versioning, even the best  administrator risks losing track of changes, lost time on debugging.  And many places do not offer any form of version control for system administrators!

In this post, I’ll explain how to run your own Subversion version control server to control your script development.  This is an update to this post for Subversion 1.4.5 … →