|
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
=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
