[Sommaire] [Imprimer]

   1  ====================================
   2   Installing the Horde 3.1 Framework
   3  ====================================
   4  
   5  :Last update:   $Date: 2006/08/15 09:30:43 $
   6  :Revision:      $Revision: 1.90.6.16 $
   7  :Contact:       horde@lists.horde.org
   8  
   9  .. contents:: Contents
  10  .. section-numbering::
  11  
  12  This document contains instructions for installing the Horde Framework on your
  13  system.
  14  
  15  The Horde Framework, by itself, does not provide any significant end user
  16  functionality; it provides a base for other applications and tools for
  17  developers. When you have installed Horde as described below, you will
  18  probably want to install some of the available Horde applications, such as
  19  IMP_ (a webmail client), or Kronolith_ (a calendar). There is a list of Horde
  20  applications and projects at http://www.horde.org/projects.php.
  21  
  22  If you are interested in developing applications for Horde, there is developer
  23  documentation and references available at http://dev.horde.org/, and some
  24  tutorials and papers on Horde available at http://www.horde.org/papers/.
  25  
  26  For information on the capabilities and features of Horde, see the file
  27  README_ in the top-level directory of the Horde distribution.
  28  
  29  .. _IMP: http://www.horde.org/imp/
  30  .. _Kronolith: http://www.horde.org/kronolith/
  31  
  32  
  33  Obtaining Horde
  34  ===============
  35  
  36  The Horde Framework can be obtained from the Horde website and FTP server, at
  37  
  38     http://www.horde.org/horde/
  39  
  40     ftp://ftp.horde.org/pub/horde/
  41  
  42  Or, better yet, use a mirror that is closer to you.  The mirror list can be
  43  found at:
  44  
  45     http://www.horde.org/mirrors.php
  46  
  47  The FTP directory contains the Horde PHP files which can be unpacked using
  48  ``tar`` and ``gunzip`` (see `Installing Horde`_, below).
  49  
  50  Bleeding-edge development versions of Horde and its applications are available
  51  via CVS; see the file `docs/HACKING`_, or visit the website
  52  http://www.horde.org/source/, for information on accessing the Horde CVS
  53  repository.
  54  
  55  You will probably also want one or more Horde applications, since Horde
  56  doesn't do much by itself; a list of available applications, with links to
  57  descriptions and downloads, can be found at
  58  
  59     http://www.horde.org/projects.php
  60  
  61  While previous versions of Horde were numbered to correspond with a particular
  62  version of the IMP webmail application, that is no longer true as of Horde
  63  version 2.0. The current version of Horde will work with the current version
  64  of Horde applications. For more information about which versions are
  65  compatible see http://www.horde.org/source/versions.php.
  66  
  67  
  68  Quick Install
  69  =============
  70  
  71  These are very terse instructions how to install Horde and its prerequisites
  72  on a LAMP sytem.  They are addressed to experienced administrators who know
  73  exactly what they are doing.  For more detailed instructions, start reading
  74  below at Prerequisites_.
  75  
  76  1. Compiling PHP for Apache::
  77  
  78       cd php-x.x.x/
  79       ./configure --with-apxs=/usr/sbin/apxs \
  80                   --with-gettext --with-dom --with-mcrypt \
  81                   --with-iconv --enable-mbstring=all --enable-mbregex \
  82                   --with-gd --with-png-dir=/usr --with-jpeg-dir=/usr \
  83                   --with-mime-magic=/user/share/misc/magic.mime \
  84                   [--with-mysql|--with-pgsql|--with-oci8|--with-ldap]
  85       make
  86       make install
  87  
  88  2. Restart Apache.
  89  
  90  3. Install PEAR packages::
  91  
  92       pear install -o Log Mail Mail_Mime DB Date File
  93       pear -d preferred_state=beta install -a Services_Weather
  94  
  95  4. Extract tarball::
  96  
  97       cd /usr/local/apache/htdocs
  98       tar zxvf /path/to/horde-x.y.z.tar.gz
  99       mv horde-x.y.z horde
 100  
 101  5. Configure Horde::
 102  
 103       cd config/
 104       for f in *.dist; do cp $f `basename $f .dist`; done
 105  
 106  6. Create database tables::
 107  
 108       cd ../scripts/sql
 109       vi create.mysql.sql
 110       mysql -u root -p < create.mysql.sql
 111  
 112  7. Test Horde::
 113  
 114       http://your-server/horde/test.php
 115  
 116  8. Finish configuration::
 117  
 118       http://your-server/horde/
 119  
 120     Go to Adminstration => Setup => Horde
 121  
 122  
 123  Prerequisites
 124  =============
 125  
 126  The following prerequisites are **REQUIRED** for Horde to function properly.
 127  
 128  1. A webserver that supports PHP.
 129  
 130     Horde and its applications are developed under the Apache webserver, which
 131     we recommend. Apache is available from
 132  
 133        http://httpd.apache.org/
 134  
 135     Horde has also been reportedly used successfully under Microsoft IIS, among
 136     others.
 137  
 138  2. PHP 4.3.0 or above.
 139  
 140     PHP is the interpreted language in which Horde is written.
 141     You can obtain PHP at
 142  
 143        http://www.php.net/
 144  
 145     Follow the instructions in the PHP package to build PHP for your system. If
 146     you use Apache, be sure to build PHP as a library with one of the following
 147     options::
 148  
 149         --with-apache
 150         --with-apxs
 151         --with-apxs2
 152  
 153     options to ``./configure``, and not as a standalone executable.
 154  
 155     The following PHP options are **REQUIRED** by Horde (listed with their own
 156     prerequisites and configure options). In many cases, the required libraries
 157     and tools can be obtained as packages from your operating system vendor.
 158  
 159     a. Gettext support. ``--with-gettext``
 160  
 161        Gettext is the GNU Translation Project's localization library.
 162        Horde uses gettext to provide local translations of text displayed by
 163        applications. Information on obtaining the gettext package is available
 164        at
 165  
 166           http://www.gnu.org/software/gettext/gettext.html
 167  
 168        See also note below on configuring Translations_.
 169  
 170     b. XML and DOMXML support. ``--with-dom``
 171  
 172        Horde's help engine and component setup require XML support. While some
 173        webservers (including recent Apache versions) have XML libraries
 174        built-in, others will require the expat XML parser libraries, available
 175        from
 176  
 177          http://expat.sourceforge.net/
 178  
 179        .. Important:: You must have **both** XML libraries installed for Horde
 180                       to work properly!
 181  
 182        Older versions of PHP also require ``--with-xml`` to enable the
 183        SAX XML functions. With recent versions of PHP, this is enabled
 184        by default.
 185  
 186     The following PHP options are **RECOMMENDED** to enable advanced features in
 187     Horde:
 188  
 189     a. A preferences container.
 190  
 191        Horde applications can store user preferences in an SQL database, an
 192        LDAP directory, an IMSP server, a Kolab server, or in PHP sessions.
 193  
 194        For SQL database preferences storage, Horde is thoroughly tested on
 195        MySQL (``--with-mysql``) and PostgreSQL (``--with-pgsql``) and has been
 196        reported to work with Oracle (``--with-oci8``) and SQL Server
 197        (``--with-mssql``).  It may also work with any other database supported
 198        by PEAR, but they are untested.
 199  
 200        Preferences can also be stored via LDAP (``--with-ldap``), Kolab
 201        (``--with-ldap``), and IMSP.
 202  
 203        Alternatively, preferences can be stored in PHP sessions, which
 204        requires no external programs or configure options, but which will not
 205        maintain preferences between sessions.
 206  
 207        While the LDAP, database, Kolab, or IMSP server need not be running on
 208        the machine onto which you are installing Horde, the appropriate
 209        client libraries to access the server must be available locally.
 210  
 211        If a preference container is not configured, no preference options
 212        will be configurable via Horde's web interface - the default values
 213        stored in each applications ``config/prefs.php`` file will be used.
 214  
 215     b. Mcrypt support ``--with-mcrypt``
 216  
 217        Mcrypt is a general-purpose cryptography library which is broader and
 218        significantly more efficient (FASTER!) than PHP's own cryptographic
 219        code. You can obtain mcrypt from
 220  
 221           http://mcrypt.sourceforge.net/
 222  
 223        Building PHP without mcrypt support will not stop Horde from working,
 224        but will force it to use weaker (and much slower) encryption.
 225  
 226     c. UTF-8 support ``--with-iconv --enable-mbstring=all --enable-mbregex``
 227  
 228        If these extensions are enabled, Horde can support multibyte character
 229        sets like UTF-8 (meaning that content with any charset can be viewed
 230        with any translation).
 231  
 232     d. GD support ``--with-gd``
 233  
 234        Horde will use the GD extension to perform manipulations on image data
 235        through the Horde_Image library.
 236  
 237        If you want GD to be able to work with PNG images, you should use the
 238        ``--with-png-dir`` option to make sure PHP can find the PNG libraries
 239        it needs to compile.
 240  
 241        If you want GD to be able to work with JPEG images, you should use the
 242        ``--with-jpeg-dir`` option to make sure PHP can find the JPEG libraries
 243        it needs to compile.
 244  
 245        You can also use the ImageMagick_ package to do these manipulations
 246        instead.  See the ``Image Manipulation`` tab of the Horde setup for more
 247        details.
 248  
 249        .. _ImageMagick: http://www.imagemagick.org
 250  
 251     e. MIME Magic support ``--with-mime-magic``
 252  
 253        Horde will use the MIME Magic extension to guess the MIME type of files
 254        by analyzing their contents.
 255  
 256        .. Note:: This extension is reported to be deprecated_ in favor of the
 257                  fileinfo PECL extension (see below).  However, some users have
 258                  reported that the fileinfo extension will not build correctly
 259                  on their system. If so, then the MIME Magic extension should
 260                  be used instead. Pick one or the other - there is no need to
 261                  compile both.
 262  
 263        If using PHP 4.3.0 -> 4.3.1, you should use ``--enable-mime-magic``
 264        instead of ``--with-mime-magic``.
 265  
 266        .. _deprecated: http://www.php.net/mime_magic
 267  
 268     .. Important:: Additionally, individual Horde applications may **REQUIRE**
 269                    or **RECOMMEND** other options to be built into PHP
 270                    also. Please check ``docs/INSTALL`` for all applications you
 271                    wish to use to see if other PHP options are needed.
 272  
 273  3. Additional PEAR Modules
 274  
 275     PEAR is short for "PHP Extension and Application Repository".  The goal of
 276     PEAR is to provide a means of distributing reusable code.
 277  
 278     For more information, see http://pear.php.net/
 279  
 280     .. Important:: Make sure you are running a supported (i.e. new enough)
 281                    version of PEAR: use the test script described below under
 282                    "`Configuring Horde`_".  Do **not** use the PEAR version
 283                    from ftp.horde.org.
 284  
 285     Check that the path where the PEAR packages are installed are part of the
 286     ``include_path`` parameter that PHP uses to find PEAR packages.
 287  
 288     Run the command::
 289  
 290       pear config-show
 291  
 292     You will see something like::
 293  
 294       PEAR directory                 php_dir         /usr/share/php
 295  
 296     Now open the php.ini file of your system, for example ``/etc/php.ini``,
 297     find the ``include_path`` and make sure that ``/usr/share/php`` is part of
 298     the list.  If you had to change that value, restart the web server after
 299     saving ``php.ini``.
 300  
 301     These PEAR modules are **REQUIRED** to be installed for complete Horde
 302     functionality:
 303  
 304     a. Log
 305     b. Mail
 306     c. Mail_Mime
 307  
 308        To install, enter the following at the command prompt::
 309  
 310          pear install Log Mail Mail_Mime
 311  
 312     These PEAR modules are **RECOMMENDED** to be installed:
 313  
 314     a. DB (>= 1.6.0)
 315  
 316        **REQUIRED** as soon as you want or need to store anything in a database.
 317        To install, enter the following at the command prompt::
 318  
 319          pear install DB
 320  
 321        To upgrade, enter the following at the command prompt::
 322  
 323          pear upgrade DB
 324  
 325     b. File
 326  
 327        **REQUIRED** only if you wish to import CSV files.
 328        To install, enter the following at the command prompt::
 329  
 330          pear install File
 331  
 332     c. Date
 333  
 334        **REQUIRED** only if you are dealing with calendar data.
 335        To install, enter the following at the command prompt::
 336  
 337          pear install Date
 338  
 339     d. Services_Weather (>= 1.3.1)
 340  
 341        **REQUIRED** only if you wish to use the weather.com block on
 342        the portal page.
 343        To install, enter the following at the command prompt::
 344  
 345          pear -d preferred_state=beta install -a Services_Weather
 346  
 347        Additional steps are required if you want use the METAR weather block on
 348        the portal page. See the file ``data/Services_Weather/buildMetarDB.php``
 349        in your PEAR directory for details.
 350  
 351     This method of installing PEAR modules requires that you have a PHP version
 352     that has been compiled as a static binary.  All versions of PHP 4.3.0+
 353     build both a SAPI module (Apache, CGI, etc.) and a command-line (CLI)
 354     binary at the same time.  Check if you have a php binary in
 355     ``/usr/local/bin`` (``/usr/bin`` if if you installed from an operating
 356     system package) before recompiling.
 357  
 358     If you receive the error ``Could not read cmd args`` you should run the pear
 359     script this way::
 360  
 361       php -d register_argc_argv=1 _PEAR_ install _MODULE_
 362  
 363     _PEAR_ is the complete path of the pear script installed by PHP during
 364     installation (e.g. ``/usr/local/bin/pear``).  Make sure the ``pear`` script
 365     appears in your path. The default installation path for pear is
 366     ``/usr/local/bin/pear``.
 367  
 368     _MODULE_ is the PEAR module, listed above, which you wish to install.
 369  
 370     For more detailed directions on installing PEAR modules, see the PEAR
 371     documentation at http://pear.php.net/manual/
 372  
 373  4. Additional PECL Modules
 374  
 375     PECL is short for "PHP Extension Community Library".  The goal of PECL is
 376     to provide a means of easily distributing PHP extensions.
 377  
 378     For more information, see http://pecl.php.net/
 379  
 380     PECL is the "sister" of PEAR and uses the same packaging and distribution
 381     system as PEAR, so the configuration/setup is essentially identical to the
 382     PEAR instructions above.
 383  
 384     When you install a PECL extension, you have to add it to your ``php.ini``
 385     so it gets loaded.  Add the following line to your ``php.ini`` file to load
 386     the extension (the extension should be installed in the directory specified
 387     by the ``extension_dir`` option in ``php.ini``)::
 388  
 389       extension=fileinfo.so
 390  
 391     Or on Windows::
 392  
 393       extension=fileinfo.dll
 394  
 395     After that, restart your webserver.
 396  
 397     These PECL modules are **RECOMMENDED** to be installed:
 398  
 399     a. fileinfo
 400  
 401        Allows Horde modules to guess the MIME type of files by analyzing
 402        their contents.
 403  
 404        If not enabled, Horde will use its own PHP code to perform MIME magic
 405        lookups.  However, this lookup is slower, less accurate, and detects
 406        fewer MIME types than the PECL extension will.
 407  
 408        To install, enter the following at the command prompt::
 409  
 410          pear install fileinfo
 411  
 412     These PECL modules are **RECOMMENDED** to be installed if you need
 413     advanced functionality:
 414  
 415     a. memcache
 416  
 417        If using the memcached SessionHandler, the memcache PECL extension must
 418        be installed.
 419  
 420        To install, enter the following at the command prompt::
 421  
 422          pear install memcache
 423  
 424     For additional help on using the pear command-line program to install PECL
 425     extensions, see the PEAR installation section above.
 426  
 427  
 428  The following non-PHP prerequisites are **RECOMMENDED**, or are **REQUIRED**
 429  if you use a specific Horde application (as noted in [brackets]):
 430  
 431  1. Sendmail or equivalent.
 432  
 433     Horde uses sendmail, or a program that implements the ``sendmail(8)`` API
 434     (as included with postfix, qmail, and exim, among others). If your system
 435     does not already have a full mail transport with a sendmail interface, you
 436     can configure Horde to speak directly with a remote SMTP server, but this
 437     may incur a performance penalty.
 438  
 439  
 440  Installing Horde
 441  ================
 442  
 443  Horde is written in PHP, and must be installed in a web-accessible directory.
 444  The precise location of this directory will differ from system to system. If
 445  you have no idea where you should be installing Horde, install it directly
 446  under the root of your webserver's document tree.
 447  
 448  
 449  Installing from Release Tarballs
 450  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 451  
 452  Since Horde is written in PHP, there is no compilation necessary; simply
 453  expand the distribution where you want it to reside and rename the root
 454  directory of the distribution to whatever you wish to appear in the
 455  URL. Please note that the default configuration expects Horde to be installed
 456  in the directory ``/horde`` though. For example, with the Apache webserver's
 457  default document root of ``/usr/local/apache/htdocs``, you would type::
 458  
 459     cd /usr/local/apache/htdocs
 460     tar zxvf /path/to/horde-x.y.z.tar.gz
 461     mv horde-x.y.z horde
 462  
 463  You would then find Horde at the URL::
 464  
 465     http://your-server/horde/
 466  
 467  Skip the next paragraph if you installed Horde from a release tarball.
 468  
 469  
 470  Installing from CVS or Snaphots
 471  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 472  
 473  At this point, the Horde framework modules need to be checked out from CVS and
 474  installed. This must be done as root (or another user with sufficient
 475  administrator priviledges)::
 476  
 477     cd horde
 478     cvs co framework
 479     cd framework
 480     php -q install-packages.php
 481  
 482  For Windows systems - use the ``install-packages.bat`` file instead.
 483  For Debian systems - the command-line PHP interpreter might be called ``php4``
 484  instead of ``php``.
 485  
 486  
 487  Configuring Horde
 488  =================
 489  
 490  1. Configuring the web server
 491  
 492     Horde requires the following webserver settings. Examples shown are for
 493     Apache; other webservers' configurations will differ.
 494  
 495     a. PHP interpretation for files matching ``*.php``::
 496  
 497           AddType application/x-httpd-php .php
 498  
 499        .. Note:: The above instructions may not work if you have specified PHP
 500                  as an output filter with ``SetOutputFilter`` directive in
 501                  Apache 2.x versions.  In particular, Red Hat 8.0 and above
 502                  Apache 2.x RPMS have the output filter set, and **MUST NOT**
 503                  have the above ``AddType`` directive added.
 504  
 505     b. ``index.php`` as an index file (brought up when a user requests a URL for
 506        a directory)::
 507  
 508           DirectoryIndex index.php
 509  
 510  2. Creating databases
 511  
 512     The specific steps to create a preferences storage container depend on
 513     which database you've chosen to use.
 514  
 515     First, look in ``scripts/sql/`` to see if a ``create.`` script already
 516     exists for your database.  If so, you should be able to simply execute that
 517     script as superuser in your database.  Consult the ``scripts/sql/README``
 518     file for more information.
 519  
 520     Be sure to change the default password, ``horde``, to something else before
 521     creating the tables! (Remember to use this password when you configure
 522     Horde in the next step.)
 523  
 524     If such a script does not exist, you'll need to build your own, using the
 525     files ``horde_users.sql``, ``horde_prefs.sql``, and ``horde_datatree.sql``
 526     as a starting point.  If you need assistance in creating databases for a
 527     database for which no ``create.`` script exists, you may wish to let us
 528     know on the `Horde mailing list`_.
 529  
 530     If you are going to use database based sessions, create a table using the
 531     files ``scripts/sql/horde_sessionhandler*.sql`` as a starting point.
 532  
 533     .. _`Horde mailing list`: horde@lists.horde.org
 534  
 535  3. Configuring Horde
 536  
 537     To configure Horde, change to the ``config/`` directory of the installed
 538     distribution, and make copies of all of the configuration ``.dist`` files
 539     without the ``.dist`` suffix::
 540  
 541        cd config/
 542        for f in *.dist; do cp $f `basename $f .dist`; done
 543  
 544     Or if you are installing Horde an a Windows system::
 545  
 546        cd config
 547        copy *.dist *.
 548  
 549     .. Note:: You only need the ``hooks.php`` file if you want to create custom
 550               hooks for some of Horde's features and default values. Beside
 551               that, this file only contains examples that you should not use as
 552               they are. If you don't need hooks it's a good idea to remove this
 553               file now::
 554  
 555                     rm hooks.php
 556  
 557     Documentation on the format of those files can be found in each file.
 558  
 559     .. Warning:: All configuration files in Horde are PHP scripts that are
 560                  executed by the web server. If you make an error in one of
 561                  these files, Horde might stop working. Thus it is always a
 562                  good idea to test the configuration files after you edited
 563                  them. If you want to test mime_drivers.php for example run::
 564  
 565                     php -l mime_drivers.php
 566  
 567  4. Testing Horde
 568  
 569     Once you have configured your webserver, PHP, and Horde, bring up the
 570     included test page in your Web browser to ensure that all necessary
 571     prerequisites have been met. If you installed Horde as described above, the
 572     URL to the test page would be::
 573  
 574        http://your-server/horde/test.php
 575  
 576     Check that your PHP and PEAR versions are acceptably recent, that all
 577     required module capabilities are present, and that ``magic_quotes_runtime``
 578     is set to ``Off``. Then note the ``Session counter: 1`` line under ``PHP
 579     Sessions``, and reload the page. The session counter should increment.
 580  
 581     If you get a warning like ``Failed opening '/path/to/test.php' for
 582     inclusion``, make sure that the web server has the permission to read the
 583     ``test.php`` file.
 584  
 585  5. Completing Configuration
 586  
 587     You can now access Horde without a password, and you will be logged in as
 588     an administrator. You should first configure a real authentication backend.
 589     Click on ``Setup`` in the ``Administration`` menu and configure
 590     Horde.  Start in the ``Authentication`` tab.
 591  
 592     Here is an example for configuring authentication against a remote IMAP
 593     server.  Similar steps apply for authenticating against a database, an LDAP
 594     server, etc.
 595  
 596     a. In the ``Which users should be treated as administrators`` field enter a
 597        comma separated list of user names of your choosing. This will control
 598        who is allowed to make configuration changes, see passwords, potentially
 599        add users, etc.
 600  
 601     b. In the ``What backend should we use for authenticating users to Horde``
 602        pulldown menu select ``IMAP authentication``. The page will reload and
 603        you will have specific options for IMAP authentication.
 604  
 605     c. In the ``Configuration type`` pulldown menu select ``Separate values``.
 606        The page will reload with additional options. Fill in the remaining
 607        three fields appropriately:
 608  
 609        - IP name/number of the IMAP server
 610        - For a secure connection, select port 993.
 611        - Select the protocol; for a secure connection either ``imap/ssl`` or
 612          ``imap/ssl/novalidate-cert`` (for self-signed certificates).
 613  
 614     Continue to configure Horde through all the tabs of the setup interface and
 615     click on ``Generate Horde Configuration``. Important items that you
 616     probably want to configure are the ``Preference System`` that lets users
 617     save their personal options, and the ``DataTree System`` that is required
 618     for some applications to work at all.
 619  
 620     Configuration of applications in ``registry.php`` is documented in the
 621     ``INSTALL`` file of each application.  Most applications require you to
 622     configure them with a "Horde administrator" account.  A Horde administrator
 623     account is any normal Horde account that has been added to the
 624     administrator list in the ``Authentication`` tab of the Horde setup.
 625  
 626     The other files in that directory need only be modified if you wish to
 627     customize Horde's appearance or behaviour -- the defaults will work at most
 628     sites.
 629  
 630  6. Securing Horde
 631  
 632     a. Passwords
 633  
 634        Some of Horde's configuration files contain passwords which local users
 635        could use to access your database.  It is recommended to ensure that at
 636        least the Horde configuration files (in ``config/``) are not readable to
 637        system users.  There are ``.htaccess`` files restricting access to
 638        directories that do not need to be accessed directly; before relying on
 639        those, ensure that your webserver supports ``.htaccess`` and is
 640        configured to use them, and that the files in those directories are in
 641        fact inaccessible via the browser.
 642  
 643        An additional approach is to make Horde's configuration files owned by
 644        the user ``root`` and by a group which only the webserver user belongs
 645        to, and then making them readable only to owner and group.  For example,
 646        if your webserver runs as ``www.www``, do as follows::
 647  
 648           chown root.www config/*
 649           chmod 0440 config/*
 650  
 651     b. Sessions
 652  
 653        Session data -- including hashed versions of your users' passwords, in
 654        some applications -- may not be stored as securely as necessary.
 655  
 656        If you are using file-based PHP sessions (which are the default), be
 657        sure that session files are not being written into ``/tmp`` with
 658        permissions that allow other users to read them. Ideally, change the
 659        ``session.save_path`` setting in ``php.ini`` to a directory only
 660        readable and writeable by your webserver.
 661  
 662        Additionally, you can change the session handler of PHP to use any
 663        storage backend requested (e.g. SQL database) via the ``Custom Session
 664        Handler`` tab in the Horde setup.
 665  
 666     For more information about securing your webserver, PHP and Horde, see the
 667     `docs/SECURITY`_ file.
 668  
 669  7. Entering the survey
 670  
 671     If you like, go to http://www.horde.org/survey/ and enter the details of
 672     your system.
 673  
 674  
 675  Configuring Applications
 676  ========================
 677  
 678  A list of available Horde applications can be found at
 679  
 680     http://www.horde.org/projects.php
 681  
 682  Instructions on configuring Horde applications can be found in the ``INSTALL``
 683  file in the application's ``docs/`` directory.
 684  
 685  
 686  Temporary Files
 687  ===============
 688  
 689  Various Horde applications will generate temporary files in PHP's temporary
 690  directory (see the ``General`` tab in the Horde setup).  For various reasons,
 691  some of these files may not be removed when the user's session ends. To
 692  reclaim this disk space, it may be necessary to periodically delete these old
 693  temporary files.
 694  
 695  An example cron-based solution can be found at ``scripts/temp-cleanup.cron``.
 696  Another possible solution is to use Red Hat's ``tmpwatch`` utility or anything
 697  similar to remove old files (see http://www.redhat.com/).
 698  
 699  
 700  Translations
 701  ============
 702  
 703  Note for international users: Horde uses GNU gettext to provide local
 704  translations of text displayed by applications; the translations are found in
 705  the po/ directory.  If a translation is not yet available for your locale (and
 706  you wish to create one), see the ``horde/po/README`` file, or if you're having
 707  trouble using a provided translation, please see the
 708  `horde/docs/TRANSLATIONS`_ file for instructions.
 709  
 710  
 711  Obtaining Support
 712  =================
 713  
 714  If you encounter problems with Horde, help is available!
 715  
 716  The Horde Frequently Asked Questions List (FAQ), available on the Web at
 717  
 718    http://www.horde.org/faq/
 719  
 720  The Horde Project runs a number of mailing lists, for individual applications
 721  and for issues relating to the project as a whole. Information, archives, and
 722  subscription information can be found at
 723  
 724    http://www.horde.org/mail/
 725  
 726  Finally, Horde developers, contributors and users also make occasional
 727  appearances on IRC, on the channel #horde on the freenode Network
 728  (irc.freenode.net).
 729  
 730  Please keep in mind that Horde is free software written by volunteers.
 731  For information on reasonable support expectations, please read
 732  
 733    http://www.horde.org/support.php
 734  
 735  Thanks for using Horde!
 736  
 737  The Horde Team
 738  
 739  
 740  .. _README: ?f=README.html
 741  .. _docs/HACKING: ?f=HACKING.html
 742  .. _docs/SECURITY: ?f=SECURITY.html
 743  .. _`horde/docs/TRANSLATIONS`: ?f=TRANSLATIONS.html