Let's start with something easy to get warm. A quick run through the administration tools.
config/
directory: conf.php
, prefs.php
, mime_drivers.php
, application specific files$conf['vhosts'] = true
config/conf.php
, config/www.example.com-conf.php
, etcCustom login or logout pages
$conf['auth']['alternate_login'] = 'http://www.example.com/mylogin.php';
imp/scripts/cutom_login.php
Custom email headers, signatures, trailers
Composite authentication
config/prefs.php
$_prefs
, grouping in $prefGroups
The swiss army knife of Horde manipulation
Classics: email address, full name
Real world example: custom preferences through web service
Real world example: force users to accept a TOS and change passwords on login
Real world example: request preference defaults, enforce TOS, normalize user names
More hooks and possible use cases
mail/blacklistFrom
, mail/showBlacklist
, etc.contacts
API.tickets
API.Registering an application at the Horde registry config/registry.php
:
Create an API definition in lib/api.php
:
Using APIs to use Horde functionality in your own applications
Using APIs to use Horde functionality in your own applications
lib/Auth/mydriver.php
turba/lib/Driver/mydriver.php