| Summary | More flexible config file organization |
| Queue | Horde Base |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | fp (at) khamsa (dot) net |
| Created | 12/07/2006 (6786 days ago) |
| Due | |
| Updated | 11/09/2008 (6083 days ago) |
| Assigned | |
| Resolved | 11/09/2008 (6083 days ago) |
| Milestone | Horde 4.0 |
| Patch | No |
State ⇒ Rejected
Version ⇒ HEAD
Queue ⇒ Horde Base
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ make configuration files system administrator oriented
Queue ⇒ Horde Framework Packages
State ⇒ New
and maintained by using a text editor because in the same file there
are too much configuration line all consecutive (not grouped and/or
separated by \n) and without any comments.
From the system administrator point of view, that want to maintain by
hand and not using the web configuration interface, multiple separated
configuration files would be really better.
The system administrator managing the application prefer to put his
configuration files clean, well commented and organized and put under
a version control system (like svn or cvs).
For this reason, imho, having multiple configuration files grouped by
their functionality would be a really good enanchments for improving
the maintenance of an horde installations.
I would suggest to have:
conf.php
conf.d/
conf.d/drivers_authentication.php
conf.d/drivers_datatree.php
conf.d/drivers_prefs.php
conf.d/drivers/etc
In this way a system administrator is allowed to maintain it's own
configuration files clean and well separated.
An example of good configurations managed that way is the debian
apache2 configuration mode.
Have a look on it, would be a very great improvement for the
maintenance of the system.