Horde Configuration OSCON July 25, 2002.…

      Horde Configuration

             OSCON

      July 25, 2002. San Diego

Chuck Hagenbuch 
Slide 1/11                                                                                   July 25, 2002
                                            Introduction
    The Horde Application Framework and its applications have a large number of configuration files.
    Users frequently have questions about which they need to edit, what configuration options, do, etc.

    We'll try and hit the most interesting and useful bits.




                                                       -2-
Slide 2/11                                                                                          July 25, 2002
                                            Config Files
    Every configuration file, in Horde and its applications, is distributed as filename.php.dist.

    We've got a lot of config files, just for Horde:

    o horde.php
    o html.php
    o mime_drivers.php
    o mime_mappings.php
    o motd.php
    o nls.php
    o prefs.php
    o registry.php
    Many of these are the same for every app once we've explained them for Horde.




                                                       -3-
Slide 3/11                                                                                       July 25, 2002
                                             horde.php
Preferences
    horde.php is the main Horde configuration file. This is where you configure global options, like the
    debugging level, and all of the global Horde backends, such as preferences, logging, a mailer, and
    optional things like the VFS and a Category backend.

    You can store preferences in either a SQL database, an LDAP         server, or only keep them for the
    length of a user's session. Here's a SQL configuration:
      

    A basic LDAP configuration might look like this. However, you are likely going to need to consult
    additional documentation to use LDAP, since setting up the necessary schema, for example, is
    non-trivial.
      

    Session-based preferences are simple and useful for demo sites or pure-kiosk sites.

Configuring Any Horde SQL backend:
      

    SQL configuration - for Turba addressbookes, categories, the VFS, Whups, anything - all follows the
    same pattern as the prefs example above. Let's look at it again:
      

    Note that we've changed two things: it's $conf['auth'], not $conf['prefs'], and we've changed the table
    name. This is what you'll need to do for any Horde SQL backend - and ALWAYS double check
    those two changes.




                                                     -4-
Slide 4/11                                                                                       July 25, 2002
                                              html.php
    html.php is where most of the look and feel of Horde - fonts, colors, sizes, etc. - is defined. Horde
    uses all CSS for defining layout, so in this file, you can control the look of pretty much anything. It
    is simply an associative array, which gets parsed by a script into CSS which is then fed to the
    browser. An example line looks like this: