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:21]
razvan
tutorials:horde_groupware [2009/08/07 21:46]
razvan
Line 15: Line 15:
 === 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
Line 72: Line 72:
 ==== Create database and tables === ==== Create database and tables ===
  
-The database configuration step {{{(1)}}} should run smoothly. However, the {{{'​Create database or tables'​}}} step {{{(2)}}} failed for me everytime as I had the database ​already created. As such I used the {{{$HORDE_INSTALL_DIR/​scripts/​sql/​groupware.mysql.sql}}} script:+The database configuration step {{{(1)}}} should run smoothly. However, the {{{'​Create database or tables'​}}} step {{{(2)}}} failed for me everytime as I had already created ​the database. As such I used the {{{$HORDE_INSTALL_DIR/​scripts/​sql/​groupware.mysql.sql}}} script:
  
 {{{ {{{
Line 143: Line 143:
 === 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 ==
Line 149: Line 149:
 === 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 159: Line 159:
 }}} }}}
  
-As mentioned [http://​www.horde.org/​source/​modules.php|on the site], the tag for wicked'​s stable branch is FRAMEWORK_3,​ and this is what we will checkout:+As mentioned ​[[http://​www.horde.org/​source/​modules.php|on the site]], the tag for wicked'​s stable branch is {{{FRAMEWORK_3}}}, and this is what will checkout:
  
 {{{ {{{
Line 176: Line 176:
 }}} }}}
  
-Run the wicked test.php script (http://​SERVER_ROOT/​WEBROOT/​wicked/​test.php). It should complain you do not have the Text_Wiki PEAR package installed. If you have privileges, you could use 'pear install'. Otherwise, use manual downloading:​+Run the wicked test script ({{{http://​SERVER_ROOT/​WEBROOT/​wicked/​test.php}}}). It should complain you do not have the {{{Text_Wiki}}} [[http://​pear.php.net/​|PEAR]] package installed. If you have privileges, you could use {{{pear install}}}. Otherwise, use manual downloading:​
  
 {{{ {{{
Line 200: Line 200:
 }}} }}}
  
-==== Enable ​creole ​markup ====+==== Enable ​Creole ​markup ====
  
-To enable Creole markup, use the configuration menu in the Administrative user interface.+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 at user level, through the use of the configuration interface for each user.+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, you would like automatic configuration of the {{{Default Identity}}} (sender address). For that we use a postauthentication script, as mentioned [[http://​wiki.horde.org/​CustomizingPreferences|here]] (search {{{David Komanek}}}). Update {{{$HORDE_INSTALL_DIR/​config/​hooks.php}}} with the script. Also update the postauthenticate configuration in $HORDE_INSTALL_DIR/​config/​conf.php}}}+When using IMP, like automatic configuration of the {{{Default Identity}}} (sender address). For that use a postauthentication script, as mentioned [[http://​wiki.horde.org/​CustomizingPreferences|here]] (search {{{David Komanek}}}). 
 + 
 +Update {{{$HORDE_INSTALL_DIR/​config/​hooks.php}}} with the script. Also update the postauthenticate configuration in {{{$HORDE_INSTALL_DIR/​config/​conf.php}}}:
  
 {{{ {{{
Line 218: Line 220:
 ==== Change default theme ==== ==== Change default theme ====
  
-File to update: {{{$HORDE_INSTALL_DIR/​config/​prefs.php}}} +File to update: {{{$HORDE_INSTALL_DIR/​config/​prefs.php}}}; 
- +Preference to alter: {{{'​theme'​}}} (I like {{{'​silver'​}}});
-Preference to alter: {{{'​theme'​}}} (I like {{{'​silver'​}}})+
  
 {{{ {{{
Line 230: Line 231:
 ==== Change default sidebar width === ==== Change default sidebar width ===
  
-As the sidebar is quite small, I like updating it from {{{150}}} to {{{200}}}.+As the sidebar is quite small, I like updating it from {{{150}}} to {{{200}}}
  
-File to update: {{{$HORDE_INSTALL_DIR/​config/​prefs.php}}} +File to update: {{{$HORDE_INSTALL_DIR/​config/​prefs.php}}}; 
- +Preference to alter: {{{'​sidebar_width'​}}};
-Preference to alter: {{{'​sidebar_width'​}}}+
  
 {{{ {{{
Line 243: Line 243:
 ==== 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}}}; 
- +Preference to alter: {{{'​sending_charset'​}}};
-Preference to alter: {{{'​sending_charset'​}}}+
  
 {{{ {{{
Line 255: Line 254:
 ==== 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}}}; 
- +Preference to alter: {{{'​delhide'​}}};
-Preference to alter: {{{'​delhide'​}}}+
  
 {{{ {{{
Line 267: Line 265:
 ==== 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}}}; 
- +Preferences to alter: {{{'​first_week_day'​}}},​ {{{'​twentyFour'​}}},​ {{{'​date_format'​}}},​ {{{'​timezone'​}}};
-Preferences to alter: {{{'​first_week_day'​}}},​ {{{'​twentyFour'​}}},​ {{{'​date_format'​}}},​ {{{'​timezone'​}}}+
  
 {{{ {{{
Line 294: Line 291:
 ==== 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, ​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 308: Line 305:
 }}} }}}
  
-==== Enable ​creole ​markup ====+==== Enable ​Creole ​markup ====
  
-The Administration -> Setup -> Wicked menu enable ​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.txt · Last modified: 2009/08/07 21:46 by razvan