<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=481362621-02062006><FONT face=Arial color=#0000ff size=2>Ok,
does anyone know if anyone has already created a guide for using subversion with
Asterisk?</FONT></SPAN></DIV>
<DIV><SPAN class=481362621-02062006><FONT face=Arial color=#0000ff size=2>I've
hit a wall already, where the subversion docs say that your files _must_ go into
a directory called trunk(huh? What's with that?). That's going to break
Asterisk, who obviously wants conf files in /etc/asterisk.</FONT></SPAN></DIV>
<DIV><SPAN class=481362621-02062006><FONT face=Arial color=#0000ff
size=2>Grrrrr.</FONT></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Watkins, Bradley
[mailto:Bradley.Watkins@compuware.com]<BR><B>Sent:</B> Friday, June 02, 2006
3:06 PM<BR><B>To:</B> Asterisk Users Mailing List - Non-Commercial
Discussion<BR><B>Subject:</B> RE: [Asterisk-Users] Config Revision
Control<BR><BR></FONT></DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff
size=2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=901410121-02062006><FONT face=Arial color=#0000ff size=2>-
Brad</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <B>On Behalf Of </B>Douglas
Garstang<BR><B>Sent:</B> Friday, June 02, 2006 4:43 PM<BR><B>To:</B>
Asterisk Users Mailing List - Non-Commercial Discussion<BR><B>Subject:</B>
[Asterisk-Users] Config Revision Control<BR><BR></FONT></DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2>Has anyone got any neat solutions for Asterisk .conf file revision
control?</FONT></SPAN></DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2>Doug.</FONT></SPAN></DIV>
<DIV><SPAN class=044363620-02062006></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=044363620-02062006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV></BLOCKQUOTE>=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.
</BLOCKQUOTE></BODY></HTML>