>My situation is this: I have a custom Web CMS (in PHP/MySQL) installed and
>running on four servers -- presently when I make an update, I have to manually
>upload the affected files to the four servers and, truth be told, I'm lazy...
>so it's a pain.
>
>I'd like to be able to make the change and then push those changes to all of the
>necessary servers. Does Subversion have the capacity to do this (or anything
>remotely similar)? Is this a feature even offered by source control tools
>today? If no to both of those, is there anywhere else I could look, or am I
>just SOL?
>
>
I've done something similiar where I had an auto-update process using
SVN as the transfer mechanism to the server.
As it was necessary to test stuff on a non production server
beforehand, I setup a process where I could push a version number file
to any of the machines and the machines would note a change in this
file and feed the version number into "svn up -r $number" to do the
update. You could do this via a daemon or a cronjob or whatever.
This way I could roll back and forward on the test server without
messing with the production servers until a change was deemed ready.
In this case the only extra load on the server was "stat"ing a small
text file every couple seconds.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 29 23:51:21 2004