With the elements above, Config::Model generates interactive
configuration editors (with integrated help and data validation)
and support several kinds of user interface, e.g. graphical, interactive
command line. See the list of available user interfaces
Using this project, a typical configuration editor will be made of 3
parts :
The user interface ( cme program and some other optional modules)
The validation engine which is in charge of validating all the configuration information provided by the user. This engine is made of the framework provided by this module and the configuration description (often referred as "configuration model", this could also be known as a schema).
The storage facility that store the configuration information (currently several backends are provided: ini files, perl files)
The important part is the configuration model used by the validation
engine. This model can be created or modified with a graphical editor
(cme meta edit
provided by Config::Model::Itself).
Don't we already have some configuration validation tools ?
You're probably thinking of tools like webmin. Yes, these tools exist
and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script
which performs semantic validation and often ends up being quite
complex (e.g. 2500 lines for Debian's xserver-xorg.config script which
handles xorg.conf file).
In most cases, the configuration model is expressed in instructions
(whatever programming language is used) and interspersed with a lot of
processing to handle the actual configuration data.
What's the advantage of this project ?
Config::Model projects provide a way to get a validation engine where
the configuration model is completely separated from the actual
processing instructions.
A configuration model can be created and modified with the graphical
interface provided by "cme meta edit" distributed with
Config::Model::Itself. The model is saved in a
declarative form (currently, a Perl data structure). Such a model is
easier to maintain than a lot of code.
The model specifies:
the structure of the configuration data (which can be queried by generic user interfaces)
the properties of each element (boundaries check, integer or string, enum like type ...)
the default values of parameters (if any)
mandatory parameters
Warning conditions (and optionally, instructions to fix warnings)
on-line help (for each parameter or value of parameter)
So, in the end:
maintenance and evolution of the configuration content is easier
user will see a common interface for all programs using this project.
upgrade of configuration data is easier and sanity check is performed
audit of configuration is possible to check what was modified by the user compared to default values
All these interfaces are generated from the configuration model.
And configuration model can be created or modified with a graphical
user interface ("cme meta edit")
What about configuration data storage ?
Since the syntax of configuration files vary wildly form one program
to another, most people who want to use this framework will have to
provide a dedicated parser/writer.
Nevertheless, this project provides a writer/parser for some common
format: ini style file and perl file.
