[Asterisk-Users] Config Revision Control

[Bruce Reeves]

Are you following the quickstart in the SVN book? For the first time to
import them in to a "folder" called trunk. Then as Aaron stated you can
check or co the trunk to any folder.

On 6/2/06, Douglas Garstang <dgarstang at oneeighty.com> wrote:
>
> Aaron,
>
> I'm trying to check-in (is that the right term?) the files for the first
> time. There's nothing in the repository yet.
>
> Doug.
>
> > -----Original Message-----
> > From: Aaron Daniel [mailto:amdtech at shsu.edu]
> > Sent: Friday, June 02, 2006 3:34 PM
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: RE: [Asterisk-Users] Config Revision Control
> >
> >
> > No, if you do an "svn co
> > http://svn.server.com/svn/configs/trunk asterisk"
> > in /etc, it'll make a folder called asterisk in your /etc
> > directory.  Once
> > that's done, any modifications made that are committed to the
> > server can
> > be downloaded into /etc/asterisk by running "svn up" inside
> > the directory.
> >
> > Might need to get your brakes checked if you keep hitting walls :)
> >
> > On Fri, 2 Jun 2006, Douglas Garstang wrote:
> >
> > > Ok, does anyone know if anyone has already created a guide
> > for using subversion with Asterisk?
> > > 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.
> > > Grrrrr.
> > >
> > > -----Original Message-----
> > > From: Watkins, Bradley [mailto:Bradley.Watkins at compuware.com]
> > > 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
> > >
> > > -----Original Message-----
> > > From: asterisk-users-bounces at lists.digium.com
> > [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of
> > Douglas Garstang
> > > Sent: Friday, June 02, 2006 4:43 PM
> > > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > > Subject: [Asterisk-Users] Config Revision Control
> > >
> > >
> > > 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.
> > >
> > >
> >
> > --
> > Aaron Daniel
> > Computer Systems Technician
> > Sam Houston State University
> > amdtech at shsu.edu
> > (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
> >
> _______________________________________________
> --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
>



-- 
Bruce
Nortex Networks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060602/bb4cffc6/attachment.htm