Subversion supports repository access over an SSH tunnel. That is good news because the first "S" in SSH stands for secure. So the next question is how do we configure Subversion to use SSH?

Unix users are usually familiar with SSH; it has supplanted telnetd as the de facto shell daemon. For this reason we will not cover svn+ssh on Unix here - there are existing resources for that. This article will explain exactly how to svn+ssh on Windows.

During a recent project for one of my clients I had a revelation of sorts: most applications are missing multi-version support.

Paltry object versioning features places unacceptable limits on our learning, testing and creativity. By object versioning I mean file revisions, memento assertions and project versions to name a few.

While your text editor may do the enormous feat of a backup version e.g. ThingEnumerator.rb~ - how well does it support switching between the two? Extending this concept to a software project - how well does your IDE support multiple project versions? What if you need to work on different releases simultaneously?

For those of you who use GNU Arch over an SFTP channel - say at Fourbucks - you will inevitably drop a connection during a transaction. Whenever TLA begins a transactional command it acquires a revision lock...and releases the lock upon completion. If the underlying channel is lost then you are left with revision lock and no way to commit to the archive.

If that happens do not use some of the snake-oil methods from this common search stream. Instead use the mechanisms that are build into TLA: