On Thu, Feb 23, 2012 at 10:35 AM, Waseem Shahzad <waseem.shah...@curemd.com> wrote: > One more thing. > >>> What do you mean with this? Is it describing the parts of your software >>> which need to be deployed or your ideas how you could deploy with >>> subversion? > > --- Yes , your ideas how you could deploy with subversion?
Some people do run live production servers on a subversion working copy and trigger svn updates or switches in post-commit hooks on the subversion server, but it is not really designed for that. For most purposes it would be better to use subversion for development with a separate testing/deployment step. For example you might use jenkins (http://jenkins-ci.org/) to run automated test and deployment jobs when in notices that changes have been commited, or simply do a manual checkout on a staging system and then use rsync with the -C option to push the changes to your production server(s). -- Les Mikesell lesmikes...@gmail.com
