Let's boil down your requirements:
- For every script, be able to vary its configuration for each virtual host.
- Manage as few files as possible.
- Prevent users of different virtual hosts from changing each other's files.
With that set of requirements, you seem to have the best solution: a default config for each script, with the ability to override it for each virtual host. The only thing I could add is that you may want to make the overriding more fine-grained. You could do this by converting the scripts to use a config system that supports option overriding, like AppConfig, or you could generate the config files from simpler templates, so that the user managing a particular virtual host just fills out a form or something and your program generates the approriate script-specific configs.
-
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.
|