On Mon, 7 May 2012, Nunya Biznatch wrote:
It is my intention to do everything from the command line. However,
there will be times when I'll have Interns coming in and doing some of
the MAC activities, and I thought this might be an easier way for the
day to day to get done.
Sounds like a recipe for hard to find problems to me.
You'll change something, they'll change something, something will be
broken.
I'd suggest one or the other.
Personally, I like plain text configuration files because I can annotate
them with a modification history showing what I* changed, when, and why.
I can also use tools like 'diff' to compare working to broken
configurations.
I back up all of the configuration files for all of the hosts** for all of
the clients I administer every day. Each host runs a script to stuff
everything I think is important into a tarball and email it to a 'backup'
email address at my office. If I really trash something on a client host,
I can always get the last known good files.
I have the tarballs going back 5 years so if a client every said 'hey,
remember when you did...' I can pull a rabbit out of my hat.
*) I usually work alone or in small (2-4) teams.
**) I skip hosts that are supposed to be exact clones of other hosts.
--
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards [email protected] Voice: +1-760-468-3867 PST
Newline Fax: +1-760-731-3000
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
