Translation(s): none

(!) [:/Discussion:Discussion]


Horde is a web application Framework.

?TableOfContents(2)

Installing Horde

 # aptitude install horde3

Read /usr/share/doc/horde3/README.Debian.

Note that Apache is installed by default but you can use another HTTP server. For example, for lighttpd:

 # aptitude install horde3 lighttpd php5-cgi

Configuring your HTTP server

For Apache, in your ?VirtualHost file (perhaps 000-default), secure (mod_access, mod_ssl, ...) and enable Horde access. For example:

Alias /horde3 /usr/share/horde3
<Directory /usr/share/horde3>
    Options FollowSymLinks
    AllowOverride Limit
    deny from all
    allow from YOUR_IP
</Directory>

If you don't use "Alias /horde3", you need update $webroot variable in registry.php file. With "Alias /foo", set 'webroot' => '/foo' and if /usr/share/horde3 is your documentroot, set 'webroot' => ' ' .

For Lighttpd, ensure cgi and alias module are enabled and add:

$HTTP["remoteip"] == "YOUR_IP" {
        alias.url += ( "/horde3/" => "/usr/share/horde3/" )                
}

Secure /etc permissions:

# chgrp www-data /etc/horde
# chmod 750 /etc/horde

Configuring Horde

http://pkg-horde.alioth.debian.org/pics/horde-setup-1.png

When your web access is secure, remove the second and third lines from /etc/horde/horde3/conf.php file and prepare file permissions for web configuration :

# chmod 777 /etc/horde/horde3/conf.php
# touch /etc/horde/horde3/conf.php.bak
# chmod 777 /etc/horde/horde3/conf.php.bak

Prepare your log file :

# touch /var/log/horde/horde3.log
# chown root.www-data /var/log/horde/horde3.log
# chmod 770 /var/log/horde/horde3.log

Prepare your backend. For example, if you use a local MySQL server, change password and inject this file :

# gunzip < /usr/share/doc/horde3/examples/scripts/\
sql/create.mysql.sql.gz \
| mysql -u MYSQL_ADMIN -p

Then your are ready to browse Horde setup in http(s?)://YOUR_SERVEUR/horde3

http://pkg-horde.alioth.debian.org/pics/horde-setup-4.png

With default configuration, you MUST configure the database, the preferences system and the users. If you fail to configure the users, you WILL NOT be able to log in. In addition, these parameters need more attention:

Generate your configuration and change permissions of configuration files :

# chmod 644 /etc/horde/horde3/conf.php
# chmod 600 /etc/horde/horde3/conf.php.bak

Now you can authorize all clients in your web server configuration.

Upgrading Horde

Secure your web server access and begin the upgrade. Change permissions for conf.php and conf.php.bak and regenerate configuration. Adjust permissions and re-open web server access.

Of course this method is also valid for sarge-to-etch upgrade.

Installing and configuring IMP

IMP is a webmail client.

For security reasons, disable IMP in /etc/horde/horde3/registry.php file, and install:

 # aptitude install imp4

Note APT installs PHP IMAP extension (reload your http server after install) and libc-client (you can probably ignore debconf question about it).

Now prepare file permissions for web configuration:

# chmod 777 /etc/horde/imp4/conf.php
# touch /etc/horde/imp4/conf.php.bak
# chmod 777 /etc/horde/imp4/conf.php.bak

Generate your configuration (GPG/PGP, user constraints, enable spam/ham report, hooks...).

Change permissions of configuration files:

# chmod 644 /etc/horde/imp4/conf.php
# chmod 700 /etc/horde/imp4/conf.php.bak

And specify your mail server(s) in /etc/horde/imp4/servers.php file. There are a lot of examples in original files (don't forget to remove/comment examples).

When you are ready, enable IMP in /etc/horde/horde3/registry.php file and verify if all is right.

Installing and configuring Ingo

Ingo is a mail filter component for IMP.

For security reasons, disable Ingo in /etc/horde/horde3/registry.php file, and install:

 # aptitude install ingo1

Prepare file permissions for web configuration:

# chmod 777 /etc/horde/ingo1/conf.php
# touch /etc/horde/ingo1/conf.php.bak
# chmod 777 /etc/horde/ingo1/conf.php.bak

Generate your configuration, it's easy because there are a few minor parameters. And specify your backend(s) in /etc/horde/ingo1/backends.php file. Backend could be null (apply rules on demand) or rules for Sieve, Procmailor or Maildrop. Here is classic backends.php file:

$backends['imap'] = array(
    'driver' => 'null',
    'preferred' => 'example.com',
    'hordeauth' => true,
    'params' => array(),
    'script' => 'imap',
    'scriptparams' => array()
);

Change permissions of configuration files:

# chmod 644 /etc/horde/ingo1/conf.php
# chmod 700 /etc/horde/ingo1/conf.php.bak

When you are ready, enable Ingo in /etc/horde/horde3/registry.php file and verify if all is right.

Installing and configuring Turba

Turba is a contact management.

For security reasons, disable Turba in /etc/horde/horde3/registry.php file, and install:

 # aptitude install turba2

Prepare file permissions for web configuration:

# chmod 777 /etc/horde/turba2/conf.php
# touch /etc/horde/turba2/conf.php.bak
# chmod 777 /etc/horde/turba2/conf.php.bak

Generate your configuration, it's easy because there are only four parameters (cache could be broken in some situation then you should disable it).

Change permissions of configuration files:

# chmod 644 /etc/horde/turba2/conf.php
# chmod 700 /etc/horde/turba2/conf.php.bak

And specify your backend(s) in /etc/horde/turba2/sources.php file. There are a lot of examples in original files (don't forget to remove/comment examples).

Example for browse Debian LDAP with all developers:

$cfgSources['debianldap'] = array(
    'title' => _("Debian Adress Book"),
    'type' => 'ldap',
    'params' => array(
        'server' => 'db.debian.org',
        'root' => 'ou=users,dc=debian,dc=org',
        'dn' => array('uid'),
        'objectclass' => array('top',
                               'debianDeveloper'),
        'charset' => 'utf-8',
        'version' => 3
    ),
    'map' => array(
        '__key' => 'dn',
        'name' => 'gecos',
        'firstname' => 'cn',
        'lastname' => 'sn',
        'nickname' => 'uid'
    ),
    'search' => array(
        'name',
        'lastname',
    ),
    'export' => true,
    'browse' => true
);

Note that using LDAP source, you will be sure to have LDAP extension for PHP and PEAR Net::LDAP (php-net-ldap package).

When you are ready, enable Turba in /etc/horde/horde3/registry.php file and verify if all is right.

Installing and configuring Kronolith

Kronolith is a calendar component.

For security reasons, disable Kronolith in /etc/horde/horde3/registry.php file, and install:

 # aptitude install kronolith2

Prepare file permissions for web configuration:

# chmod 777 /etc/horde/kronolith2/conf.php
# touch /etc/horde/kronolith2/conf.php.bak
# chmod 777 /etc/horde/kronolith2/conf.php.bak

Generate your configuration. Most important choice is storage driver. You will probably choose SQL driver, with Default Horde parameters. You need now create SQL tables. For example, if you use a local MySQL server:

# mysql -u MYSQL_ADMIN -p DATABASE < \
  /usr/share/doc/kronolith2/examples/scripts/sql/kronolith.mysql.sql

Change permissions of configuration files:

# chmod 644 /etc/horde/kronolith2/conf.php
# chmod 700 /etc/horde/kronolith2/conf.php.bak

When you are ready, enable Kronolith in /etc/horde/horde3/registry.php file and verify if all is right.

Installing and configuring Gollem

Gollem is a file manager.

 # aptitude install gollem

Prepare file permissions for web configuration. Generate your configuration and change permissions of configuration files. And specify your backend(s) in /etc/horde/gollem/backends.php file.

Installing and configuring Nag

Nag is a task list manager.

For security reasons, disable Nag in /etc/horde/horde3/registry.php file, and install:

 # aptitude install nag2

Prepare file permissions for web configuration:

# chmod 777 /etc/horde/nag2/conf.php
# touch /etc/horde/nag2/conf.php.bak
# chmod 777 /etc/horde/nag2/conf.php.bak

Generate your configuration. Most important choice is storage driver. You will probably choose SQL driver, with Default Horde parameters. You need now create SQL tables. For example, if you use a local MySQL server:

# mysql -u MYSQL_ADMIN -p DATABASE < \
  /usr/share/doc/nag2/examples/scripts/sql/nag.sql

Change permissions of configuration files:

# chmod 644 /etc/horde/nag2/conf.php
# chmod 700 /etc/horde/nag2/conf.php.bak

When you are ready, enable Nag in /etc/horde/horde3/registry.php file and verify if all is right.

Installing and configuring Mnemo

Mnemo is a notes/memos manager.

 # aptitude install mnemo2

Prepare file permissions for web configuration. Generate your configuration and change permissions of configuration files.

Installing and configuring Forwards

Forwards is an autoforward component.

# aptitude install sork-forwards-h3

Prepare file permissions, and generate configuration with Horde setup. Choose how you want to setup your forward email address (FTP, LDAP, SQL...).

Installing and configuring Vacation

Vacation is autovacation component.

# aptitude install sork-vacation-h3

Prepare file permissions, and generate configuration with Horde setup. If you use Vacation with vacation package, don't forget to correct vacation path to '/usr/bin/vacation' and use 'Berkeley DB 4.x hash, (little|big) endian' for type of database. Don't forget to adjust file permissions. Choose how you want to setup your vacation (FTP, LDAP). An easy way is to install ftp package.

Installing and configuring Passwd

Passwd is a module for users to change their password.

# aptitude install sork-passwd-h3

Prepare file permissions, and generate configuration with Horde setup. Choose backends in /etc/horde/passwd3/backends.php file to set up password (LDAP, SQL, SMB, Poppassd, Expect, Vmailgr, Vpopmail, Pine...)

Installing and configuring SAM

SAM is a module for users to change their spam prefs.

# aptitude install horde-sam

Prepare file permissions, and generate configuration with Horde setup. And specify your backend in /etc/horde/sam/backends.php file (LDAP or SQL for Amavis, SQL or FTP for ?SpamAssassin).