This doesn't need to be an explicit feature in Analog- the existing
configuration file structure (using CONFIGFILE for instance) is pretty
much adequate for this type of operation.
always included: default.conf
(contains defaults, can be overridden)
choose one: site1.conf, site2.conf, site3.conf
(specifies logfiles, outputfiles, "local" formats, etc.)
choose one: weekly-report.conf, daily-report.conf, etc.
(turns on/off specific reports, etc.)
always included: mandatory.conf
(contains unalterable settings for everyone)
Then just make sure you explicitly specify which config file to use for
each particular report. Since you're probably going to use a script to
drive things in any serious hosting setup, this is a piece of cake. (if
you can't handle scripting and you're "mass" hosting, you're in trouble)
Just spend some time thinking about what config directives should be in
each included file and you'll be golden.
Analog's configurations could use a tiny bit of tweeking and I'd love
to see more "levels" of configurability, but it's not vital. What you're
asking for is better handled outside of the core application. Since analog
only rarely makes significant changes to the config file format, using
that as justification is just silly.
Once/if Analog starts generating more than one output per dataset I'll
agree that some sort of "mapping" will probably be needed. But until then
(and that's been on the to-do list for a long long time now) I don't think
it should/will happen.
-=Jim=-
> It would be nice if instead of generate one analog.conf for each
> virtual host, implement some way have analog.conf pointing to a
> virtual host map file, containing only location of logs, location of
> output etc.
>
> Then when appears a new release only should change the master
> analog.conf And add a virtual host only will be needed to add a line
> on the virtual host map file.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
