Edward M. Goldberg

Cloud Computing and SVN Checkout in the form of an “export” is a very good match.

Let me start with an outline of the basic ideas.  You need to store all of the code and content for your server or servers in a safe place.  This is NOT on the server.  If the server dies or is attacked you need to put back the code.  You could say that is is a code backup.  But that is not exactly correct.

SVN is the Master or “Gold” repository for the code and you are making a code distribution.

Once you have all of the code in the SVN tree.  All you need to due when the server is deployed is to export the SVN tree “on top” of the server.   The content in the master SVN is then on the server and you are ready to start any post install scripts you need.

The good parts are:

1. The code you own is in your SVN “GOLD” file collection is SVN under lock and key.
2. The steps to install from SVN to your new server is a simple SVN EXPORT of the tree.
3. The cost is very low.

The bad parts:

1. You need to set up a SVN for the deployment of the project and keep it up to date.
2. If the SVN is down you can not launch a new server,
3. More working parts to maintain.

Once you have all of the process in place.  You will have a very simple commend to deploy a new server.  Ever change and update will be logged.  All of the code and data will be safe and stored is several places.  So if later you need a copy of the code you will not be stuck.  If you rely on eht code and data on a server one day that server my die and out are out of luck!

Edward M. Goldberg

Tags:   Content · Deploy · Server Launch · SVNNo Comments