PUBLIC MARKS from camel with tags share & subversion

Sharing code between projects is still not a trivial matter with subversion. Especially if you are familiar with SourceSafe, you will find that subversion makes it hard to share code. Subversion seems to be really great in creating a version mess and good in solving one, but the reason I need source code control is to prevent such a mess. This is where subversion can be greatly improved, but it is not impossible. This howto will demonstrate a directory setup that takes the subversion sharing mechanism into account, as well as other issues that repositories bring.

In this article, Prabhakar Chaganti will show us to create virtual appliances that perform one specific function. These appliances can be web servers, database servers or anything else that you can think of which is useful for your business. The key advantage with these appliances is the fact that they are mostly maintenance free, and can be started up and then used without going through any lengthy installation process. You can use these as needed for your testing and then dispose them off. You can also use them for staging environments or production environments, and you can even share them across the enterprise.