Hi,

I do this using XML files, that I read with XML::Simple and a Perl Module that handles some XML tags, like <include file="someother.xml"/>

Then I split my configs by several files, with options specific to some thing, and used by all needed parts.

Then I make config files to the tools that just include the splits each tool need.

I try to change the splits as little as possible, and usually just to add new options. When I need to restructure the options tree to one of the tools, I just restructure the main xml file for that particular tool, repositioning the includes (which are just the leafs in each branch).

This is for sysadm/offline tools. When talking about websites, I use a table in the site database where all options are saved, and where I can edit them.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.