[dev] default backends
Jan Schneider
jan at horde.org
Mon Feb 14 13:01:22 UTC 2011
Zitat von Ronan SALMON <rsalmon at mbpgroup.com>:
>> commit a0c1ee118b71c24b4ecb12da20606822490992ec
>> Author: Jan Schneider <jan at horde.org>
>> Date: Sat Feb 12 18:43:18 2011 +0100
>>
>> Provide default backends.php where it makes sense. Add configuration
>> options to allow administrators to pick the backends to use.
>
> IMHO, there is no need for a configuration options to allow
> administrators to pick the backends to use. It is much simpler for
> an admin to only configure the needed backends rather than having to
> configure the one you need and then go through the GUI to disabled
> the other ones.
>
> Looking at turba backends.php, not everyone need all backends
> configured by default and then enabled/disabled through the admin
> GUI, ie :
> $cfgSources['localsql']
> $cfgSources['localldap']
> $cfgSources['personal_ldap']
> $cfgSources['prefs']
> $cfgSources['favourites']
> $cfgSources['facebook']
> $cfgSources['imsp']
> $cfgSources['kolab_global']
> $cfgSources['kolab']
>
> This configurations should be provided as examples (commented out),
> except localsql ? If someone need any one of them, then they can be
> configured thought backends.local.php.
>
> this should avoid errors and speed login process.
No, the current setup works now for 99% of the installations without
any administrator interaction.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
More information about the dev
mailing list