Comments on: Subversion http://www.phpvs.net ASP.Net and PHP go head to head Tue, 24 Jan 2012 07:03:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: John Collins http://www.phpvs.net/articles/blakes-centos-lamp-server-guide/subversion/comment-page-1/#comment-10630 John Collins Fri, 08 May 2009 09:30:13 +0000 http://www.phpvs.net/articles/blakes-centos-lamp-server-guide/subversion/#comment-10630 One thing you might want to consider is using Subversion on your server to implement version control for your Apache/PHP/MySQL configuration files. This gives some real advantages: 1. You can just have an SVN client installed on the server, and have your repo containing your config files elsewhere. If you make the required changes in the repo, you then only need to run "svn update" on the production server, which will pull down the changes. In this way you are effectively using Subversion as a deployment mechanism. 2. If there are any issues with your new config, you can always easily roll back to a previous version. 3. You have a complete history of all changes made to your configuration. 4. Replicating the same configuration across multiple servers becomes trivial. One thing you might want to consider is using Subversion on your server to implement version control for your Apache/PHP/MySQL configuration files. This gives some real advantages:

1. You can just have an SVN client installed on the server, and have your repo containing your config files elsewhere. If you make the required changes in the repo, you then only need to run "svn update" on the production server, which will pull down the changes. In this way you are effectively using Subversion as a deployment mechanism.
2. If there are any issues with your new config, you can always easily roll back to a previous version.
3. You have a complete history of all changes made to your configuration.
4. Replicating the same configuration across multiple servers becomes trivial.

]]>