These solutions are meant for mid to large scale remote deployment of fixed versions.
I suppose the actual management of config files is primarily done with templates° and must - if properly done - be adjusted for every new software version. This pays off when scalability matters.
But the ability to adjust to an extended config file of a new version for a single installation will be limited, especially if it comes in the OP's shown form of a default cfg where one is supposed to uncomment options.
In this case
- storing the old default
- alarming about diffs
- adjusting the template manually
might be the only pragmatic solution to have some efficiency.
°) please correct me otherwise!
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.