Last time we looked at multiple projects which was a nice way of serving more than one project from the same repository.
But what if we wanted our projects to be completely separated? Well, serving multiple repositories is the answer.
Now we have the subversion repository created and you can access the repository nice and securely using the SSH protocol (see Using SSH with svnserve).
So what happens when you want to run version control on another project?
In the introduction to svnserve article, we configured svnserve and secured it against unauthorised access.
However, one problem was that the connection was not encrypted. This would be fine over an Office LAN or other trusted network, but not if we are using an untrusted network such as the internet. Using the SSH protocol is the answer.
Following on from the Introduction to Subversion article, we'll now look at svnserve (subversion's built in server).
Svnserve allows you to access your project from remote machines. Concentrating on configuration and basic setup, this article introduces this often overlooked programme.
Remember the version of your website or application that worked? Just before you tried to add that new feature?
Enter version control. Subversion is an excellent version control system that allows you to roll back to earlier versions of an application and even share the code among different developers.