[Horde 4]: Horde 4 and later is distributed through the PEAR installer. See the installation documentation for details.
[Horde 3]: Go to our Download Page.
All components which have never seen a stable release are available through Git (CVS for Horde 3). Step-by-step directions for obtaining them with Git or CVS are available on the Horde website.
(Please keep in mind that anything that hasn't seen a stable release hasn't seen it for a reason; while some of the components are functional at this point and may be capable of being used in production, they're still not quite ready in the eyes of the developers, and might be buggy in interesting and well-hidden ways.)
Nightly snapshots of all modules are also available at Snapshot site in tar formats. Since these are unattended, automatted snapshots they may not always be stable or even work at all. They are mostly intended for those who need the latest development code but do not have access to Git resp. CVS.
On some Linux distributions, it is possible to install Horde and any of its stable components from precompiled packages.
The Horde Project no longer makes our own distribution packages available.
Debian users can install IMP through their package manager as well; the IMP packages are available in the stable distribution.
Step-by-step directions for obtaining the software with Git are available on the Horde website. In addition, please note the following issues which often come up:
Step-by-step directions for obtaining the software with CVS are available on the Horde website. In addition, please note the following issues which often come up:
Upgrading from the patch files is an easy way to upgrade the code base. Note however that it is preferable to upgrade from the tar files or from CVS/rsync, as the patch files will only update the code and text files and not the binary files such as images, compiled translations, and so on.
How to upgrade via the provided patch files is operating system dependent. The following directions will work for most unix based systems. Consult your operating system software documentation for additional information or for information on using patch sets for other operating systems.
Please be aware that if any binary files were added or changed between patched versions that they will NOT be automatically updated. You will need to manually add or genenerate these binary files to your application directories. These are for example images, sounds or translations.
First, make sure you meet all the pre-requesites for the new version. See the appropriate section of this FAQ for more information.
Next, download the patch file into the directory where the software resides. For Horde use your Horde directory, for IMP use your IMP directory, and so on. The following examples will use IMP as an example, and assume you have already downloaded the patch file to the imp directory.
It is advisable, for various reasons, to stop your Horde web services before you do an upgrade, and restart them afterwards. While not always required, doing so may help provide a more successful upgrade.
cd imp gunzip patch-imp-4.0.4-4.1.gz patch -p1 < patch-imp-4.0.4-4.1
You can rebuild the compiled translations if you have all necessary packages installed:
cd po /path/to/horde/po/translation.php make --module imp --no-compendium
See po/README for details.
As the upgrade process does not change your configuration files, but rather only operates on the *.php.dist files in the configuration directories. So you will need to manually compare your configuration files to their respective *.dist version, and merge in any changes or additions needed.
Be sure to check for a file called docs/UPGRADING or docs/UPDATE for additional information such as updates to database layouts or other changes which may be needed. This file will not always exist (if no additional steps are needed when upgrading) so don't panic if it isn't there!
If you shut down your web services, then restart them at this point. Even if you did not shut down your services before the upgrade, in some cases you may need to restart your web server at this point anyway.