If all 3 servers are the same then no. I import to the svn server the check out the files on each server. I f I change a file on server A I can then commit the change to the repository, on the central server, and then do a svn update on the other 2.


On 6/2/06, Douglas Garstang <[EMAIL PROTECTED]> wrote:
Bruce,
 
But, if you have three servers that function the same, don't you have to check the file out three times and check it back in three times?
 
Doug.
-----Original Message-----
From: Bruce Reeves [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 02, 2006 3:34 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Config Revision Control

I use subversion on a central server and then store each server that is different. The purpose behind it for me was 2 fold, first I have a backup of my configs centeralized and I can roll-back any changes. Second, I can checkout a servers files on a different machine to edit them if I want and check them back when finished. What I meant by file-level is if I edit sip.conf and check it in then the whole svn goes to a new version, not just that file. We use a M$ product that has version control at the file level, so for each file in the library there is a version history.



--
Bruce
Nortex Networks
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to