| Summary | Administration -> Configuration for sites with a vhost config should modify conf-<vhost>.php |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | mike.gabriel (at) das-netzwerkteam (dot) de |
| Created | 12/04/2015 (3449 days ago) |
| Due | |
| Updated | 02/11/2016 (3380 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
you set this issue (#14179) to status "Feedback". Is that a question
into the round of developers? Or do you need any feedback from me as
the wishlist bug reporter?
Thanks+Greets,
Mike
that actually wants to edit the central conf.php? At runtime, all
conf.php files are merged, so we only know if, at this point,
someone is admin. Not if he is admin for a certain vhost.
One site scenario could be:
https://default.example.com/horde does only have a conf.php and _no_
vhost config. The admin of default.example.com can globally
administrate the Horde installation.
vhost1.example.com/horde provides a horde/conf-vhost1.example.com.php
file and in this file another admin is shipped by adding
$conf['auth']['admins'] to this horde/conf-vhost1.example.com.php.
This should override the global admin privilege and allow this vhost
admin to configure his vhost.
Another site scenario could be:
All (default) conf.php files are edited by hand (and are derived from
a default Horde installation) and all Horde instances are vhost
instances. So configuration of a vhost instance is mainly done via the
conf-<vhost>.php files. The vhost config files should only stored
parameter that are not set in the default conf.php.
If the global admin wants to modify vhosts, he needs to do this on
config file level.
Again, we need to provide the $conf['auth']['admins'] array()
populated with appropriate site admin logins.
I am aware that this could be fine-granulaed more and more (e.g. there
could be ACLs in the conf.php file so that some conf.php params are
not editable in vhosts, etc.).
The point is that at the moment, a Horde service provider cannot
delegate Horde administration in vhost scenarios at all.
that actually wants to edit the central conf.php? At runtime, all
conf.php files are merged, so we only know if, at this point, someone
is admin. Not if he is admin for a certain vhost.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Administration -> Configuration for sites with a vhost config should modify conf-<vhost>.php
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ New
configuration, I put files into /etc/horde/*/:
conf-<vhost>.php
Next, I would like to deligate administration of the <vhost> instances
to admins on site. So, any changes performed under
Settings -> Administration -> Configuration
should end up in conf-<vhost>.php (and only those options that differ
from the default conf.php).
However, admins of <vhost> instances always modify conf.php and thus
interfere with other <vhost> instances.