14 May
2007
14 May
'07
7:03 a.m.
Nils Ohlmeier wrote:
Hello everybody,
as we want to provide more examples for the configuration the following the
question came up:
Do you prefer
- one big example configuration
- probably harder to understand
- easier to maintain for us
- one example config file per "feature"
- probably easier to understand your desired "feature"
- you might have problems to integrate all your desired "features" into one
config without breaking anything
- harder to maintain for us, as we have to update several files :-)
As the configuration examples are indented to be for the community, I would
like to know what you prefer or if you see other options.
Thanks
Nils
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Ideally, I'd like to see:
-One big configuration, well documented (per line or per block at the
VERY least).
-Smaller configuration examples for options that might not fit into a
larger overall config (block-level, which blocks/modparams/etc in the
large config would be replaced with/added by the option blocks provided;
detailed documentation on the blocks and modparams and what they do/mean
(perhaps with links to the proper lines in the module documentation).
That way you're not keeping separate configs for each option (unless
it's something that completely replaces all the rest of the config), and
as more tricks/suggestions come up, it's easier to add an option or two
to the options sections since they're just small blocks of code.
Just an idea.
N.