Title: Message
Brad,
Not
sure if #include statments will help. For that to work, there would have to be a
separate directory structure for each server. I'd like to keep it as common as
possible.
If we
had, on our first pbx server...
[general] context=frompstn_start allowguest=yes
bindport=5060
#include
"binaddr.conf"
and bindaddr.conf
had:
binaddr=192.168.10.10
then it's specific to a certain host. It doesn't add
any value. I might as well just stick it in the main file. Now, if we could do some sort of variable substition,
THAT might work.
Doug.
-----Original Message----- From:
Watkins, Bradley [mailto:[EMAIL PROTECTED] Sent: Friday,
June 02, 2006 3:06 PM To: Asterisk Users Mailing List - Non-Commercial
Discussion Subject: RE: [Asterisk-Users] Config Revision
Control
The
first situation you mention can be solved by creating separate files that
contain the unique elements, and then including them in the main files where
all the commonality is. That is how we do things, and it works well for
us. It may be a little cumbersome if you have a *lot* of uniqueness, but
if you really want to share a significant portion of the configs this is the
only way I know of to do it.
As
for revision control, we use Subversion with a branch for each server
containing the unique files. All of our configuration scripts also
include automatic checkins of changed files (we can always revert if need
be). It also makes it easy to spot changes if something goes wrong, as
an svn diff will tell you.
Regards,
-
Brad
Has anyone got any neat solutions for Asterisk .conf file revision
control?
We
have multiple Asterisk boxes here, that we'd like to maintain a _mostly_
common set of conf files on. They aren't all the same though. There's subtle
differences. For example, in sip.conf, iax.conf etc, the bindaddr
setting is different. Dundi.conf is very different between each
system.
At
the moment I have a file tree on a separate server, and I use the m4
processor to replace certain unique sections of the files. I have a bunch of
scripts to build sip.conf etc and then rsync the files out to the servers.
It works, mostly, but it isn't elegant.
I'd like to revision control all this. I don't know how it could be
done with revision control though. As I said, not all the files are the
same. I don't know if we'd run a version control client on each Asterisk
box, or if we'd run it centrally, and then use rsync again, to copy the
files out.
Doug.
=00The contents of this e-mail
are intended for the named addressee only. It contains information that may be
confidential. Unless you are the named addressee or an authorized designee,
you may not copy or use it, or disclose it to anyone else. If you received it
in error please notify us immediately and then destroy it.
|
_______________________________________________
--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