No :) If you have the entire repo checked out, say, on your work box, you
can edit those files locally, and then do a commit from there. You could
even set up some sort of script that runs and updates the files remotely.
Once you've checked out a repo, you only have to check it out once and
update/commit when changes are made.
In this manner, you can have one "general" repo, which has #include's in
files that need to be modified. Those files can have the "general"
configuration that likely won't change often at all.
Then you can have separate repos for each server that'll hold an included
sip.conf file (in your case, that file may only contain "bindaddr").
Then, on the asterisk boxes, once you've checked out the general one, you
check out the non-general one specific to that box. You can include it
from a completely different directory, /usr/local/ast_includes... or
inside the directory, /etc/asterisk/includes... wherever, it doesn't
really matter :)
As long as the naming structure remains exactly the same on all the
machines, it should be a lot easier to track changes on the individual
machines this way.
On Fri, 2 Jun 2006, Douglas Garstang wrote:
But what if all the files are not the same? What if the binaddr is different in
sip.conf on each server, or what about DUNDi? That's completely different. Do
you have to go to each box one by one, check the file out, edit it, and check
it back in again? I'm trying to find a way to avoid that.
-----Original Message-----
From: Bruce Reeves [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 3:55 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Config Revision Control
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.
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
_______________________________________________
--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
