Dear all,
the first implementation of configuration directories for NaviServer,
together with updated documentation and examples, is now available in the
NaviServer repository (HEAD).
Notable changes and artefacts:
Directory-based configuration support
Configuration can now be provided either as a single Tcl file (unchanged
behavior) or as a directory containing ordered configuration fragments.
This improves maintainability and reuse for larger setups.
OpenACS configuration fully controllable via environment variables
Optional modules can now be activated or deactivated via configuration
variables, without editing configuration files. This significantly
simplifies containerized (e.g. Docker) deployments, where environment
variables are the natural control mechanism.
Sample split-up OpenACS configuration
https://github.com/naviserver-project/naviserver/blob/main/conf/openacs-config.d/README.md
<>
Updated documentation
The administrator guide now documents configuration files and
configuration directories, and includes a description of
ns_configure_variables (which has existed since 5.0 but was previously
undocumented):
https://naviserver.sourceforge.io/5.1/manual/files/admin-config.html <>
https://naviserver.sourceforge.io/5.1/naviserver/files/ns_config.html#6 <>
As mentioned before: configuration directories are entirely
optional. Existing single-file configuration files continue to work
unchanged. The recommended ordering of configuration fragments is not
mandatory, but intended as guidance only. The same applies to the
suggested granularity of configuration chunks and to variable-based
module activation - these mechanisms are optional and meant to provide
additional flexibility, not to impose a new configuration style.
Feedback is very welcome, in particular regarding:
naming and ordering of configuration fragments
the module activation model via configuration variables
Experiences and best practices from your configurations, not sufficiently
covered.
Best regards,
Gustaf
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
