User Tools

Site Tools


tutorials:horde_groupware

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tutorials:horde_groupware [2009/08/07 20:38]
razvan
tutorials:horde_groupware [2020/07/20 09:16] (current)
Line 1: Line 1:
-= Installing and configuring Horde Groupware =+====== Installing and configuring Horde Groupware ======
  
 [[http://www.horde.org/groupware/|Horde Groupware]] or [[http://www.horde.org/webmail/|Horde Webmail Groupware]] is an open-source web-based [[http://en.wikipedia.org/wiki/Category:Groupware|group management]] application. It features common tools for group/team management: calendar ([[http://www.horde.org/kronolith/|kronolith]]), address book ([[http://www.horde.org/turba/|turba]]), webmail ([[http://www.horde.org/imp/|imp]], [[http://www.horde.org/mimp/|mimp]], [[http://www.horde.org/dimp/|dimp]]), task lists ([[http://www.horde.org/nag/|nag]]), notes ([[http://www.horde.org/mnemo/|mnemo]]), wiki ([[http://www.horde.org/wicked/|wicked]]), group management, permissions, categories. It's also highly customizable, allowing you to choose themes, define your entry/portal web-page, set locales, set display preferences, etc. [[http://www.horde.org/groupware/|Horde Groupware]] or [[http://www.horde.org/webmail/|Horde Webmail Groupware]] is an open-source web-based [[http://en.wikipedia.org/wiki/Category:Groupware|group management]] application. It features common tools for group/team management: calendar ([[http://www.horde.org/kronolith/|kronolith]]), address book ([[http://www.horde.org/turba/|turba]]), webmail ([[http://www.horde.org/imp/|imp]], [[http://www.horde.org/mimp/|mimp]], [[http://www.horde.org/dimp/|dimp]]), task lists ([[http://www.horde.org/nag/|nag]]), notes ([[http://www.horde.org/mnemo/|mnemo]]), wiki ([[http://www.horde.org/wicked/|wicked]]), group management, permissions, categories. It's also highly customizable, allowing you to choose themes, define your entry/portal web-page, set locales, set display preferences, etc.
Line 5: Line 5:
 We've started using Horde Groupware for [[https://www.rosedu.org/horde|ROSEdu]] group management and for the [[https://elf.cs.pub.ro/asistent/horde|USO and RL courses]]. It is light and intuitive and, at this point, suitable for our needs. We've started using Horde Groupware for [[https://www.rosedu.org/horde|ROSEdu]] group management and for the [[https://elf.cs.pub.ro/asistent/horde|USO and RL courses]]. It is light and intuitive and, at this point, suitable for our needs.
  
-== Install and basic configuration ==+===== Install and basic configuration =====
  
 The installation and configuration process is complex but quite straightforward. Horde's {{{README}}} and {{{INSTALL}}} files and wiki and searchable mailing lists should provide all necessary answers. I've completed four installation processes, all on a Debian GNU/Linux 5.0 Lenny; the last one was accomplished while writing this tutorial to make sure I don't miss out on something. Having more than one installation experience helped me discover new features and configuration options in Horde. The installation and configuration process is complex but quite straightforward. Horde's {{{README}}} and {{{INSTALL}}} files and wiki and searchable mailing lists should provide all necessary answers. I've completed four installation processes, all on a Debian GNU/Linux 5.0 Lenny; the last one was accomplished while writing this tutorial to make sure I don't miss out on something. Having more than one installation experience helped me discover new features and configuration options in Horde.
Line 13: Line 13:
 I didn't use [[http://wiki.debian.org/Horde|Debian's internal package]], as I wanted more freedom when installing and configuring Horde. For my third and fourth installation instances, I used a non-privileged account, so it was mandatory that I installed Horde from its source package. I didn't use [[http://wiki.debian.org/Horde|Debian's internal package]], as I wanted more freedom when installing and configuring Horde. For my third and fourth installation instances, I used a non-privileged account, so it was mandatory that I installed Horde from its source package.
  
-=== System settings and requirements ===+==== System settings and requirements ====
  
-The following list shows the system configuration and setting and desired features. We want an Apache2 and MySQL based instance, with IMAPS login (based on an e-mail account) and the built-in wiki.+The following list shows the system configuration and setting and desired features. want an Apache2 and MySQL based instance, with IMAPS login (based on an e-mail account) and the built-in wiki.
  
-* Debian GNU/Linux 5.0 Lenny +   Debian GNU/Linux 5.0 Lenny 
-* Horde Webmail Groupware +   Horde Webmail Groupware 
-* non-privileged account +   non-privileged account 
-* Apache2 web-server +   Apache2 web-server 
-* MySQL +   MySQL 
-* IMAPS e-mail access +   IMAPS e-mail access 
-* IMAPS login +   IMAPS login 
-* Horde builtin wiki (wicked)+   Horde builtin wiki (wicked)
  
-=== Required packages ===+==== Required packages ====
  
 The required Debian packages are listed below. A MySQL server also has to be configured (it need not be on the same system). cvs needs only be installed for CVS-based modules (such as [[http://www.horde.org/wicked/|wicked]]). The required Debian packages are listed below. A MySQL server also has to be configured (it need not be on the same system). cvs needs only be installed for CVS-based modules (such as [[http://www.horde.org/wicked/|wicked]]).
  
-* apache2 +   apache2 
-* libapache2-mod-php5 +   libapache2-mod-php5 
-* mysql-client-5.0 +   mysql-client-5.0 
-* php5 +   php5 
-* php5-cli +   php5-cli 
-* php-pear +   php-pear 
-* php5-imap +   php5-imap 
-* cvs for CVS-based modules+   cvs for CVS-based modules
  
 === Download == === Download ==
Line 53: Line 53:
 }}} }}}
  
-=== Initial configuration ===+==== Initial configuration ====
  
 Most installation steps are described in the {{{$HORDE_INSTALL_DIR/docs/INSTALL}}} file. Most installation steps are described in the {{{$HORDE_INSTALL_DIR/docs/INSTALL}}} file.
Line 90: Line 90:
 Do not worry about the above errors. The script is ment to be run by the MySQL root user, enabling the creation of the database and user. As I had already created the database and required user, those steps were not needed. Do not worry about the above errors. The script is ment to be run by the MySQL root user, enabling the creation of the database and user. As I had already created the database and required user, those steps were not needed.
  
-==== Webroot update ====+=== Webroot update ===
  
 Because there may be problems detecting the webroot URL (happened to me every time), update the {{{$HORDE_INSTALL_DIR/config/registry.php}}} file (look for the {{{'webroot'}}} variable). In my case, this must be {{{'/~razvan/horde'}}}: Because there may be problems detecting the webroot URL (happened to me every time), update the {{{$HORDE_INSTALL_DIR/config/registry.php}}} file (look for the {{{'webroot'}}} variable). In my case, this must be {{{'/~razvan/horde'}}}:
Line 125: Line 125:
 }}} }}}
  
-=== Enable HTTPS ===+==== Enable HTTPS ====
  
 You can configure HTTPS only access to Horde through the use of {{{mod_ssl}}} and {{{mod_rewrite}}} Apache modules. Replace {{{/~razvan/horde}}} with your webroot. You can configure HTTPS only access to Horde through the use of {{{mod_ssl}}} and {{{mod_rewrite}}} Apache modules. Replace {{{/~razvan/horde}}} with your webroot.
Line 141: Line 141:
 }}} }}}
  
-=== That's it! ===+==== That's it! ====
  
 Congratulations! You now have a working instance of Horde Webmail Groupware. Accessing your base URL ({{{http://SERVER_NAME/WEBROOT/}}}) should get you to the secured login page. Congratulations! You now have a working instance of Horde Webmail Groupware. Accessing your base URL ({{{http://SERVER_NAME/WEBROOT/}}}) should get you to the secured login page.
  
-== Extra configuration and customization ==+===== Extra configuration and customization =====
  
-=== Installing wicked ===+==== Installing wicked ====
  
 As mentioned above, wicked (Horde's integrated wiki) should be installed. In order to do that we have to download the CVS version, as mentioned [[http://www.horde.org/source/using.php|on the site]] (don't forget to install {{{cvs}}}) As mentioned above, wicked (Horde's integrated wiki) should be installed. In order to do that we have to download the CVS version, as mentioned [[http://www.horde.org/source/using.php|on the site]] (don't forget to install {{{cvs}}})
Line 200: Line 200:
 }}} }}}
  
-==== Enable Creole markup ====+=== Enable Creole markup ===
  
 To enable [[http://www.wikicreole.org/wiki/Home|Creole markup]], use the configuration menu in the {{{Administrative -> Setup -> Wicked}}} user interface. See [[tutorials:horde_groupware#ui_configuration|below]]. To enable [[http://www.wikicreole.org/wiki/Home|Creole markup]], use the configuration menu in the {{{Administrative -> Setup -> Wicked}}} user interface. See [[tutorials:horde_groupware#ui_configuration|below]].
  
-=== Customization ===+==== Customization ====
  
 Certain features of Horde can be tuned either at global level, through the use of configuration files or web user interface, or at user level, through the web user interface. Certain features of Horde can be tuned either at global level, through the use of configuration files or web user interface, or at user level, through the web user interface.
  
-==== Setup automatic configuration of default identity ====+=== Setup automatic configuration of default identity ===
  
 When using IMP, I like automatic configuration of the {{{Default Identity}}} (sender address). For that I use a postauthentication script, as mentioned [[http://wiki.horde.org/CustomizingPreferences|here]] (search {{{David Komanek}}}). When using IMP, I like automatic configuration of the {{{Default Identity}}} (sender address). For that I use a postauthentication script, as mentioned [[http://wiki.horde.org/CustomizingPreferences|here]] (search {{{David Komanek}}}).
Line 218: Line 218:
 }}} }}}
  
-==== Change default theme ====+=== Change default theme ===
  
 File to update: {{{$HORDE_INSTALL_DIR/config/prefs.php}}}; File to update: {{{$HORDE_INSTALL_DIR/config/prefs.php}}};
Line 241: Line 241:
 }}} }}}
  
-==== IMP - configure default sending charset ====+=== IMP - configure default sending charset ===
  
 File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}}; File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}};
Line 252: Line 252:
 }}} }}}
  
-==== IMP - disable view of deleted messages ====+=== IMP - disable view of deleted messages ===
  
 File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}}; File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}};
Line 263: Line 263:
 }}} }}}
  
-==== Configure date and timezone options ====+=== Configure date and timezone options ===
  
 File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}}; File to update: {{{$HORDE_INSTALL_DIR/imp/config/prefs.php}}};
Line 287: Line 287:
 }}} }}}
  
-=== UI configuration ===+==== UI configuration ====
  
-==== User UI configuration ====+=== User UI configuration ===
  
 A non-admin user can alter his/hers configuration through the {{{Options -> Global Options}}} menu. The user can configure personal information, theme, sidebar width, time format, etc. A non-admin user can alter his/hers configuration through the {{{Options -> Global Options}}} menu. The user can configure personal information, theme, sidebar width, time format, etc.
  
-==== Administrative UI configuration ====+=== Administrative UI configuration ===
  
-The administrative UI configuration is enabled through the {{{Administration -> Setup}}} menus. As the admin user is altering the configuration files ({{{conf.php}}} and {{{conf.bak.php}}}), these must be writable by the web server user ({{{www-data}}} for Apache2) (the backup file must be created if it does not exist):+The administrative UI configuration is enabled through the {{{Administration -> Setup}}} menus. As the configuration files ({{{conf.php}}} and {{{conf.bak.php}}}) are altered through the web interfacethey must be writable by the web server user ({{{www-data}}} for Apache2) (the backup file must be created if it does not exist):
  
 {{{ {{{
Line 305: Line 305:
 }}} }}}
  
-==== Enable Creole markup ====+=== Enable Creole markup ===
  
 The {{{Administration -> Setup -> Wicked}}} menu enables configuration of the built-in wiki. The usual configuration I'm doing is changing the default markup to Creole (the {{{$conf[wicked][format]}}} variable). The {{{Administration -> Setup -> Wicked}}} menu enables configuration of the built-in wiki. The usual configuration I'm doing is changing the default markup to Creole (the {{{$conf[wicked][format]}}} variable).
 +
 +==== Logging ====
 +
 +By default, Horde logs information in {{{/tmp/horde}}}. Configuration can be altered through the use of the web interface ({{{Administration -> Setup -> Horde -> Logging}}}) or by using the {{{$HORDE_INSTALL_DIR/config/conf.php}}} file:
 +
 +{{{
 +$conf['log']['priority'] = PEAR_LOG_NOTICE;
 +$conf['log']['ident'] = 'HORDE';
 +$conf['log']['params'] = array();
 +$conf['log']['name'] = '/tmp/horde.log';
 +$conf['log']['params']['append'] = true;
 +$conf['log']['type'] = 'file';
 +$conf['log']['enabled'] = true;
 +}}}
tutorials/horde_groupware.1249666716.txt.gz · Last modified: 2009/08/07 20:38 by razvan