stuart: doc/www/src Makefile, 1.10, 1.11 client-features.html.m4, 1.2, 1.3 cvs-kolab.html.m4, 1.7, 1.8 default.css, 1.1, 1.2 documentation.html.m4, 1.4, 1.5 footer.html.m4, 1.14, 1.15 howto-kolab-kde-client.html.m4, 1.2, 1.3 howto-kolab.html.m4, 1.2, 1.3 howtos.html.m4, 1.3, 1.4 index.html.m4, 1.22, 1.23 kolab-plugins.html.m4, 1.7, 1.8 screenshots.html.m4, 1.1, 1.2 webclient.html.m4, 1.1, 1.2
cvs at intevation.de
cvs at intevation.de
Fri Jun 11 00:48:36 CEST 2004
Author: stuart
Update of /kolabrepository/doc/www/src
In directory doto:/tmp/cvs-serv2586
Modified Files:
Makefile client-features.html.m4 cvs-kolab.html.m4 default.css
documentation.html.m4 footer.html.m4
howto-kolab-kde-client.html.m4 howto-kolab.html.m4
howtos.html.m4 index.html.m4 kolab-plugins.html.m4
screenshots.html.m4 webclient.html.m4
Log Message:
Was planning to just split off the webclient installation instructions, but I got a bit carried away :-)
This is quite a major overhaul of the site. Updates include:
- 'last updated' timestamps on each page, so we can see how slack we're being with updates
- improved news portion of the front page (rendering tested in Konqueror & Firefox so far, seems to work fine in both)
- greatly enhanced webclient instructions
- updated client feature matrix (this could still use some work, also perhaps add in Toltec to this?)
- some small gramatical/rendering fixes on most (if not all) pages
- rendering improvements on most pages
- updated menu which links to these new/updated pages
Enjoy :-P
Index: Makefile
===================================================================
RCS file: /kolabrepository/doc/www/src/Makefile,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- Makefile 10 Jun 2004 16:23:00 -0000 1.10
+++ Makefile 10 Jun 2004 22:48:33 -0000 1.11
@@ -5,7 +5,8 @@
client-features.html \
kolab-plugins.html \
documentation.html \
- screenshots.html
+ screenshots.html \
+ webclient.html
all:
mkdir -p ../html/images ../html/howtos/amavis_spamassassin_sophos \
Index: client-features.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/client-features.html.m4,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- client-features.html.m4 28 Jan 2004 17:48:18 -0000 1.2
+++ client-features.html.m4 10 Jun 2004 22:48:34 -0000 1.3
@@ -1,97 +1,137 @@
-m4_define(`PAGE_TITLE',`Kolab Clients - Feature Matrix')
-
+m4_define(`PAGE_TITLE',`Client Feature Matrix')
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
+
+<p>This page is meant to inform users of the capabilities of the various Kolab
+clients. This is not meant to be an authoritative reference, but merely a
+basic introduction as to how the clients stack up against each other. Please
+note that as the clients are under constant development this may become out
+of date fairly quickly - if you wish to inquire about the current status of
+a feature listed below (or even one that isn't listed) then please enquire
+on the <a href="/mailman/listinfo/kolab-devel">development mailing list</a>.
+</p>
-<p><strong>Note: Last Updated in October 2003</strong></p>
<table cols="4" border="1" cellspacing="0" cellpadding="2" width="100%">
- <thead bgcolor="#ddddff">
- <th width="20%">Category</th><th width="20%">Sub-Category</th><th width="30%">KDE</th><th width="30%">Horde</th>
+ <thead>
+ <th width="10%">Category</th>
+ <th width="15%">Sub-Category</th>
+ <th width="22%">KDE Client (Kolab 1)</th>
+ <th width="22%">Kontact (Kolab 2 ~ under development)</th>
+ <th width="22%">Horde (Kolab Webclient)</th>
</thead>
<tbody>
<tr bgcolor="#ececec">
- <td width="0%">Mail</td>
- <td width="0%">IMAP</td>
- <td>Disconnected</td>
- <td>Yes</td>
+ <td width="0%">Mail</td>
+ <td width="0%">IMAP</td>
+ <td class="part">Disconnected</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
<tr>
- <td></td>
- <td>POP3</td>
- <td>Yes</td>
- <td>No</td>
+ <td></td>
+ <td>POP3</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
<tr bgcolor="#ececec">
- <td>Groupware (IMAP)</td>
- <td>Calendar</td>
- <td>Yes</td>
- <td>Partial</td>
+ <td>Groupware (IMAP)</td>
+ <td>Calendar</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
<tr>
- <td></td>
- <td>Task List</td>
- <td>Yes</td>
- <td>Yes</td>
+ <td></td>
+ <td>Task List</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
<tr>
- <td></td>
- <td>Memos</td>
- <td>Yes</td>
- <td>Yes</td>
+ <td></td>
+ <td>Memos</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
<tr>
- <td></td>
- <td>Contacts</td>
- <td>Yes</td>
- <td>Yes</td>
+ <td></td>
+ <td>Contacts</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
- <tr>
- <td></td>
- <td>Meeting Requests (Recv)</td>
- <td>Yes</td>
- <td>No</td>
+ <tr>
+ <td></td>
+ <td>Meeting Requests (Recv)</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
- <tr>
- <td></td>
- <td>Meeting Requests (Send)</td>
- <td>Yes</td>
- <td>No</td>
+ <tr>
+ <td></td>
+ <td>Meeting Requests (Send)</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
- <tr>
- <td></td>
- <td>Task Requests (Recv)</td>
- <td>Yes</td>
- <td>No</td>
+ <tr>
+ <td></td>
+ <td>Task Requests (Recv)</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="no">No</td>
</tr>
- <tr>
- <td></td>
- <td>Task Requests (Send)</td>
- <td>Yes</td>
- <td>No</td>
+ <tr>
+ <td></td>
+ <td>Task Requests (Send)</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="no">No</td>
</tr>
- <tr>
- <td></td>
- <td>Free/Busy View</td>
- <td>Yes</td>
- <td>No</td>
+ <tr>
+ <td></td>
+ <td>Free/Busy View</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
</tr>
- <tr bgcolor="#ececec">
- <td>Address Book</td>
- <td>IMAP</td>
- <td>Yes</td>
- <td>Yes</td>
+ <tr>
+ <td></td>
+ <td>Extended Free/Busy View</td>
+ <td class="no">No</td>
+ <td class="no">No</td>
+ <td class="no">No</td>
</tr>
- <tr>
- <td></td>
- <td>LDAP</td>
- <td>Yes</td>
- <td>Yes</td>
+ <tr>
+ <td></td>
+ <td>Calendar sharing</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="part">2-Step</td>
</tr>
- <tr bgcolor="#ececec">
- <td>Future</td>
- <td>IMAP IDLE</td>
- <td>No</td>
- <td>No</td>
+ <tr bgcolor="#ececec">
+ <td>Address Book</td>
+ <td>IMAP</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>LDAP</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr bgcolor="#ececec">
+ <td>Future</td>
+ <td>IMAP IDLE</td>
+ <td class="no">No</td>
+ <td class="no">No</td>
+ <td class="no">No</td>
</tr>
</tbody>
</table>
Index: cvs-kolab.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/cvs-kolab.html.m4,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- cvs-kolab.html.m4 13 May 2004 08:39:34 -0000 1.7
+++ cvs-kolab.html.m4 10 Jun 2004 22:48:34 -0000 1.8
@@ -1,643 +1,40 @@
-m4_define(`PAGE_TITLE',`Kolab Server Development')
-
+m4_define(`PAGE_TITLE', `Server Development')
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
-<h3>Anonymous CVS Access</h3>
-CVSROOT=<small><tt>:pserver:anonymous at intevation.de:/home/kroupware/jail/kolabrepository</tt></small>
-<br>
+<p>The Kolab project maintains a CVS server for version control of the Kolab
+server code. Anonymous CVS access is provided for all interested parties to
+check out the code - this can be obtained by the following means:
+<pre class="shell">
+<b>CVSROOT</b>
+ :pserver:anonymous at intevation.de:/home/kroupware/jail/kolabrepository
+</pre>
+</p>
<h3>Development Branches</h3>
<ul>
<li><strong>Stable</strong><p>
This is the current release of Kolab and is used for bugfixes.<br>
- To checkout use : <em>cvs checkout -r KOLAB_1_0</em>
+ To checkout use : <code>cvs checkout -r KOLAB_1_0</code>
</p>
</li>
<li><strong>Development</strong><p>
- Also know as HEAD this branch is open for development.<br>
- To checkout use : <em>cvs checkout</em>
+ Also know as HEAD; this branch is open for development.<br>
+ To checkout use : <code>cvs checkout</code>
</p>
</li>
</ul>
-
<h3>Web CVS Access</h3>
-Browse the Source Code <a href="http://intevation.de/cgi-bin/viewcvs-kolab.cgi">[ via viewcvs ]</a>
-
-<h3>Report results</h3>
-Please report any development issues to the public mailinglist
-<a href="mailto:kolab-devel at kolab.org">kolab-devel at kolab.org</a>.
-
-<hr />
-<h3>Kolab Webclient</h3>
-<h4>How to get it; How to configure it; How to run it.</h4>
-
-<div align="right">April 2004</div>
-
-<p>Please direct any comments and suggestions about this guide to
-<a href="mailto:s.binge at codefusion.co.za">Stuart Bingë</a></p>
-
-<h4>What's New?</h4>
-<ul>
-<li>Multiple calendar, notepad and tasklist support (each calendar, notepad and tasklist
-is stored in a separate IMAP folder).</li>
-<li>Calendar, Note and Task sharing. Currently this is a two-step process (unfortunately),
-but simplifying this to a single-step procedure is definitely on our todo. What you
-need to do is go into IMP (the Mail client), and share the folder via Cyrus ACLs.
-You then need to go into the respective application (Kronolith, Mnemo, Nag) and share
-the calendar corresponding the the IMAP folder you shared, mirroring the ACL settings
-you specified in IMP.</li>
-<li>Full filter support for mail, through the Ingo application. This also allows
-for more powerful vacation and forwarding support than the previous vacation
-and forwarding modules.</li>
-<li>No more 'meetings' application for viewing free/busy information and inviting
-attendees. All this functionality has been ported (by yours truly) to Kronolith,
-meaning all events you create in your calendar can support attendees.</li>
-<li>Many minor fixes and improvements including an improved UI, as the Horde
-project has evolved substantially as we have been developing the Webclient
-functionality. This also means that the 'Layout' option on the Horde portal
-now works - you are able to customise your front page to display mail/note/task/etc
-summaries, as well as additional blocks such as Google search, in any configuration
-that you like. There's even a Kolab theme that you can use :-)</li>
-</ul>
-
-<p><b>PLEASE NOTE:</b> The Webclient, while technically feature-complete, is still
-considered development quality. As such it is not recommended that you run
-it in a production environment, however any and all potential testers are most welcome.
-There are most probably a whole host of bugs left in the code, and a lot of improvements
-can still be made, however as it stands it is a very usable product.</p>
-
-<p>Also note
-that while this is considered the 'Kolab Webclient', it is still based on an
-existing project (the <a href="http://www.horde.org/">Horde</a> project), and
-as the current Webclient codebase is contained in Horde's CVS repository it relies
-an an underlying code base that is also under constant development. What this
-boils down to is any bugs that you may encounter might not necessarily be related
-the the Kolab Webclient portion of the code, but instead be within the Horde code
-itself.</p>
-
-<p>Currently the Webclient does not interoperate with the Kolab KDE Client, nor
-any Outlook-configured mailboxes, so any users that are to use the Webclient should
-do so exclusively. Interoperability is most definitely one of the upcoming features
-you can look forward to - even between Outlook mailboxes and the Webclient.</p>
-
-<p>Any commentary about the Webclient should be directed either to the
-<a href="http://lists.horde.org/mailman/listinfo/dev">Horde development list</a>
-or to the <a href="http://kolab.org/mailman/listinfo/kolab-devel">Kolab development list
-</a>. We should pick up discussion on either.</p>
-
-<p>This guide assumes you will be running Horde & Kolab on the same machine.
-It should technically be possible to separate the two; however, as of yet this
-has not been attempted. If you manage to do this we would greatly appreciate
-feedback as to how you did it, and we'll include it in this guide.</p>
-
-<p>This guide also assumes that your kolab installation is in <code>/kolab</code>
-- if it's not then just substitute in your specific kolab root location wherever
-you see the directory <code>/kolab</code> in this document.</p>
-
-<p>The following conventions are used, and assumptions made, in this document:
-<ul>
-<li>Commands that should be entered at the shell are preceded by hashes (<code>#</code>).</li>
-
-<li>You will be installing the Webclient as the root user.</li>
-
-<li>You installed Kolab through the <a href="http://www.zfos.org/">ZfOS</a> OBMTOOL
-method.</li>
-
-<li>You are working in the Kolab environment while installing the Webclient
-(e.g. by running <code><a href="#opa">opa</a> /kolab</code>).</li>
-
-<li>You should create a temporary directory for use in the initial setup
-steps, while the necessary packages are being downloaded - the files should
-only be moved to their final locations once everything is in place. Once
-everything is installed you can remove this temporary directory; in this
-guide <code>/tmp</code> is used as the temporary location.</li>
-
-<li>It is recommended that you put the following in your root users' <code>~/.cvsrc</code>:
-<pre>
-cvs -z3
-update -d -P
-checkout -P
-diff -u
-</pre>
-</li>
-</ul>
-</p>
-
-<h4>Pre-installation</h4>
-<p>First of all you need to ensure your Kolab distribution is able to run Horde.
-This means installing additional OpenPKG RPMs and recompiling your Apache RPM
-with additional flags. You can obtain source RPMs from the <a
-href="ftp://ftp.openpkg.org/release/2.0/SRC/">OpenPKG 2.0 Source Repository</a>, or
-if you'd prefer and are running Kolab on an OpenPKG-supported platform, you
-can obtain binary RPMs from the <a href="ftp://ftp.openpkg.org/release/2.0/BIN">
-OpenPKG 2.0 Binary Repository</a></p>
-
-<p>The necessary packages are:</p>
-
-<pre>
-libxml-2.6.6-2.0.0
-libxslt-1.1.3-2.0.0
-mysql-4.0.18-2.0.0
-</pre>
-
-<p>Apache needs to be re-compiled with the following additional flags:</p>
-
-<pre>
---with=mod_php_dom
---with=mod_php_mysql
-</pre>
-
-<p>For your convenience I've included an updated Kolab/OpenPKG 2.0 obmtool.conf in
-<a href="#obmconf">Appendix B</a> that can be used to set up a Horde-capable Kolab
-installation.
+<p>Access to the Kolab CVS server is also provided through a
+<a href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/">ViewCVS</a> interface.
</p>
-<p>Be sure to change your MySQL root password to something secure after installing
-MySQL. You can do this by running the following command:<p>
-
-<pre>
-# mysqladmin -u root password "your-mysql-root-pw"
-</pre>
-
-<h4>Optional Step</h4>
-<p>Install a PHP Accelerator.</p>
-
-<p>This step is not critical to get Horde running, however it is highly recommended
-if you want to have as responsive a Webclient as possible. This guide instructs on
-how to install the <a href="http://www.phpaccelerator.co.uk/">ionCube PHP Accelerator</a>,
-as it is exceptionally simple to set up and provides a very noticeable performance boost.
-If you prefer other accelerators and are able to get them to work with Kolab then please
-send instructions on how to install them and we'll put it up here.</p>
-
-<p>Download the relevant package for your platform and PHP version from the
-<a href="http://www.phpaccelerator.co.uk/download.php">ionCube Downloads Page</a>. As of
-time of writing for x86 Linux, this would be
-<a href="http://www.phpaccelerator.co.uk/releases/linux_i686-glibc2.1.3/1.3.3r2_4.3.0/php_accelerator-1.3.3r2_php-4.3.0_linux_i686-glibc2.1.3.tgz">1.3.3r2</a>
-for PHP version 4.3.0. You should read the INSTALL and CONFIGURATION files that are
-distributed with PHPA for details on how to fine-tune performance. If you just want to
-quickly set up an accelerated environment for use with Horde then the following commands
-should be suitable:</p>
-
-<pre>
-# cd /tmp
-# tar -xvzf php_accelerator*.tgz
-# mv php_accelerator*/php_accelerator*.so /kolab/lib
-# chown kolab:kolab /kolab/lib/php_accelerator*.so
-</pre>
-
-<p>The following then needs to be added to <code>/kolab/etc/kolab/php.ini.template</code>:
-
-<pre>
-; PHP Accelerator extension
-zend_extension="/kolab/lib/php_accelerator_1.3.3r2.so"
-
-; This should be as large as you can spare. The default is 8, which is not
-; optimal for a project as large as Horde.
-phpa.shm_size = 16
-</pre>
-
-<p>It is also recommended that you increase the value of <code>memory_limit</code> in
-<code>/kolab/etc/kolab/php.ini.template</code> to 12M or even 16M, for optimal use with
-Horde.</p>
-
-<p>After saving <code>/kolab/etc/kolab/php.ini.template</code> run <code>kolabconf</code>
-to re-generate <code>php.ini</code> and restart the Apache server. You can test to see if
-the extension is operational by viewing the following script through your Kolab web server.</p>
-
-<pre>
-<?php phpinfo(); ?>
-</pre>
-
-<p>You should see something similar to the following after the initial version information:</p>
-
-<pre>
-This program makes use of the Zend Scripting Language Engine:
-Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies
-with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002,
-by Nick Lindridge
-</pre>
-
-<p>PHP Accelerator is now installed. Any PHP script viewed through your Kolab webserver will
-have its bytecode cached by PHPA - note that if you are experiencing 'weirdness' when it
-comes to viewing in-development scripts (for example, your changes are not coming through
-or incorrect errors are being generated) then your PHPA cache may need to be refreshed.
-The easiest way to do this is to just stop Apache and <code>rm /tmp/phpa*</code>.</p>
-
-<p>Now then, on to the actual Webclient installation instructions.</p>
-
-<h4>Step 1</h4>
-<p>Download and install the necessary PEAR packages.</p>
-
-<p>1. Horde's PEAR distribution:</p>
-<pre>
-# cd /tmp
-# wget ftp://ftp.horde.org/pub/pear/pear-1.3.tar.bz2
-# tar xvjf pear-1.3.tar.bz2
-# cd pear
-# rm pearcmd.php
-# cp -R * /kolab/lib/php/
-</pre>
-
-<p>2. Miscellaneous PEAR packages from PEAR CVS (Instructions from
-<a href="http://www.php.net/anoncvs.php">http://www.php.net/anoncvs.php</a>)</p>
-
-<pre>
-# cd /tmp
-# cvs -d :pserver:cvsread at cvs.php.net:/repository login
-</pre>
-<p>(When asked for a password, use 'phpfi').</p>
-<pre>
-# cvs -d :pserver:cvsread at cvs.php.net:/repository checkout pear/HTTP_WebDAV_Client
-# pear install pear/HTTP_WebDAV_Client/package.xml
-</pre>
-
-<h4>Step 2</h4>
-<p>Check out the necessary Horde modules from Horde's CVS (instructions from
-<a href="http://www.horde.org/source/using.php">http://www.horde.org/source/using.php</a>):</p>
-
-<pre>
-# cd /tmp
-# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository login
-</pre>
-<p>(When asked for a password, use 'horde').</p>
-<pre>
-# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository checkout horde framework imp kronolith mnemo nag passwd turba ingo
-# find . -type d -name CVS | xargs rm -rf
-</pre>
-
-<h4>Step 3</h4>
-<p>Install the Horde framework:</p>
-
-<pre>
-# cd /tmp/framework
-# php install-packages.php
-</pre>
-
-<h4>Step 4</h4>
-<p>Move the default Horde configuration files to their final locations:</p>
-
-<pre>
-# cd /tmp
-# mv horde/config/conf.php.dist horde/config/conf.php
-# mv horde/config/prefs.php.dist horde/config/prefs.php
-# mv horde/config/mime_drivers.php.dist horde/config/mime_drivers.php
-# mv horde/config/html.php.dist horde/config/html.php
-# mv horde/config/nls.php.dist horde/config/nls.php
-# mv horde/config/hooks.php.dist horde/config/hooks.php
-# mv horde/config/registry.php.dist horde/config/registry.php
-# mv imp/config/html.php.dist imp/config/html.php
-# mv imp/config/mime_drivers.php.dist imp/config/mime_drivers.php
-# mv imp/config/prefs.php.dist imp/config/prefs.php
-# mv imp/config/servers.php.dist imp/config/servers.php
-# mv ingo/config/prefs.php.dist ingo/config/prefs.php
-# mv ingo/config/backends.php.dist ingo/config/backends.php
-# mv ingo/config/fields.php.dist ingo/config/fields.php
-# mv kronolith/config/html.php.dist kronolith/config/html.php
-# mv kronolith/config/prefs.php.dist kronolith/config/prefs.php
-# mv mnemo/config/prefs.php.dist mnemo/config/prefs.php
-# mv nag/config/html.php.dist nag/config/html.php
-# mv nag/config/prefs.php.dist nag/config/prefs.php
-# mv passwd/config/backends.php.dist passwd/config/backends.php
-# mv turba/config/html.php.dist turba/config/html.php
-# mv turba/config/prefs.php.dist turba/config/prefs.php
-# mv turba/config/attributes.php.dist turba/config/attributes.php
-# mv turba/config/sources.php.dist turba/config/sources.php
-</pre>
-
-<h4>Step 5</h4>
-
-<p>Some Horde configuration files need to be edited by hand; the rest
-can be auto-generated through the Horde Admin interface. You may want
-to <code>chmod 0600</code> these files for additional security. The files
-you need to edit, and what needs to be done in each file, is as follows:</p>
-
-<dl>
-<dt><code>horde/config/registry.php</code></dt>
-<dd>Delete all the <code>$this->applications['XXX']</code> blocks except the following:
-<code>$this->applications['horde']</code>, <code>$this->applications['logout']</code>,
-<code>$this->applications['problem']</code>, <code>$this->applications['imp']</code>,
-<code>$this->applications['ingo']</code>, <code>$this->applications['turba']</code>,
-<code>$this->applications['kronolith']</code>, <code>$this->applications['mnemo']</code>,
-<code>$this->applications['nag']</code> and <code>$this->applications['passwd']</code>.
-For each of these remaining blocks, delete the line that says <code>'menu_parent' => 'XXX'</code>.
-</dd>
-
-<dt><code>imp/config/servers.php</code></dt>
-<dd>Delete all the <code>$servers['XXX']</code> blocks except the
-<code>$servers['kolab']</code> definition (should be right at the end
-of the file).</dd>
-
-<dt><code>ingo/config/backends.php</code></dt>
-<dd>Delete all the <code>$backends['XXX']</code> blocks except the
-<code>$backends['kolab']</code> definition (should be right at the end
-of the file).</dd>
-
-<dt><code>passwd/config/backends.php</code></dt>
-<dd>Delete all the <code>$backends['XXX']</code> blocks except the
-<code>$backends['kolab']</code> definition (should be right at the end
-of the file).</dd>
-
-<dt><code>turba/config/sources.php</code></dt>
-<dd>Delete all the <code>$cfgSources['XXX']</code> blocks except the
-<code>$backends['kolab_global']</code> and <code>$backends['kolab_local']</code>
-definitions (should both be the last two entries in the file).</dd>
-</dl>
-
-<h4>Step 6</h4>
-<p>Move the horde directories to their final location. Note that you can put
-the Webclient in whatever directory you want and link to it from your
-Kolab WWW directory, however in this document we just move the Horde
-directories directly into the WWW directory.</p>
-
-<pre>
-# cd /tmp
-# chown -R kolab-n:kolab-n horde framework imp kronolith mnemo nag passwd turba ingo
-# mv horde /kolab/var/kolab/www/
-# mv imp kronolith mnemo nag passwd turba ingo /kolab/var/kolab/www/horde/
-</pre>
-
-<h4>Step 7</h4>
-
-<p>Install the Horde schema into OpenLDAP. This schema allows Horde preferences
-to be stored in each Kolab user's object within LDAP. Add the following to your
-<code>/kolab/etc/kolab/slapd.conf.template</code> after the existing
-schema include lines:</p>
-
-<pre>
-include /kolab/var/kolab/www/horde/scripts/ldap/horde.schema
-</pre>
-
-<p>Save the template and run <code>kolabconf</code> to update OpenLDAP to
-use the new schema file.</p>
-
-<h4>Step 8</h4>
-
-<p>Set up the Horde database in MySQL. This database is used to store general
-Horde information, as well as per-user settings such as category information, etc.
-You can also view these instructions in the <code>horde/scripts/db/README</code> file.</p>
-
-<p>You should first edit <code>/kolab/var/kolab/www/horde/scripts/db/mysql_create.sql</code>
-and change the Horde MySQL user password to something more secure. The section you need to
-edit looks like this:</p>
-
-<pre>
-REPLACE INTO user (host, user, password)
- VALUES (
- 'localhost',
- 'horde',
--- IMPORTANT: Change this password!
- PASSWORD('horde')
- );
-</pre>
-
-<p>Now add the Horde database:</p>
-
-<pre>
-# mysql --user=root --password=<b>your-mysql-root-pw</b> < /kolab/var/kolab/www/horde/scripts/db/mysql_create.sql
-# mysqladmin --user=root --password=<b>your-mysql-root-pw</b> reload
-</pre>
-
-<p>To check that this is working, the following command should execute
-without errors:</p>
-
-<pre>
-# mysql --user=horde --password=<b>your-horde-user-pw</b> horde
-</pre>
-
-<h4>Step 9</h4>
-<p>You now need to configure all the Horde applications. Log in to your Horde
-installation, at http://your.kolab.server/horde/.</p>
-
-<ul>
-<li>Click on 'Administration', then 'Configuration'. You should see a list
-of available Horde applications.</li>
-<li>Go through this list and configure each Horde application as you please.
-You may want to choose 'Logout' in the 'Select any applications
-that should be linked in XXX's menu' section for each application's configuration,
-so that there is a 'Logout' menu option on the top menu for each application.
-The following configuration options should be adhered to for each application:</li>
-<li><b>!!! WARNING !!!</b><br /><br />
-
-Be sure to configure the 'Horde' module LAST, or else you will
-be locked out of the administration interface before everything has been properly configured -
-if this happens you'll have to re-checkout horde/config/conf.php.dist from Horde CVS
-and overwrite your auto-generated horde/config/conf.php with this .dist file. Also DO NOT
-click on 'Generate Configuration' when configuring Horde until you have gone through ALL
-the configuration tabs and entered the necessary variables as specified below. If you do click
-on this prematurely then you'll most probablly encounter fatal errors when trying to view
-any Horde pages, meaning you'll have to overwrite conf.php as above, and re-configure your
-Horde module.<br /><br />
-
-<b>!!! WARNING !!!</b>
-</ul>
-
-<dl>
-<dt>Address Book (turba)</dt>
-<dd>The default configuration should prove sufficient.</dd>
-
-<dt>Calendar (kronolith)</dt>
-<dd>Select the 'Kolab' driver for both the 'Calendar' and 'Free/Busy' sections.</dd>
-
-<dt>Filters (ingo)</dt>
-<dd>The default configuration should prove sufficient.</dd>
-
-<dt>Mail (imp)</dt>
-<dd>Make sure the botton two options are checked on the 'Custom Hooks' tab.
-You may also want to specify the location of the ispell or aspell binary,
-if you have one of these installed, in the 'External Utilities and Menu'
-tab in order to allow users to spellcheck their email.</dd>
-
-<dt>Notes (mnemo)</dt>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
-
-<dt>Password (passwd)</dt>
-<dd>Uncheck the option entitled 'Should we allow the user to specify the
-username?'.</dd>
-
-<dt>Tasks (nag)</dt>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
-
-<dt>Horde (horde)</dt>
-<dd><ul><li>Select the 'Kolab' tab and configure each entry to the values pertaining to
-your specific kolab server.</li>
-<li>Under the 'Database' tab, be sure to set the 'password'
-field to whatever you specified when creating the Horde database in MySQL.</li>
-<li>In the 'Authentication' tab, select <code>IMAP</code> as the authentication backend.
-Change the 'Configration type' to <code>Separate Values</code>, and set the 'Connection Protocol'
-to <code>imap/notls</code>. You may also want to specify a Kolab account in the
-'Administrators' field, for use in configuring Horde at a later stage. If you have a
-Kolab account such as <code>horde-admin at my.kolab.domain</code>, enter it here.</li>
-<li>(Optional) Under the 'Logging' tab, change the 'Path to the log file' to
-<code>/kolab/var/horde/horde.log</code>. For this to work you'll have to do the following:
-<pre>
-# mkdir -p /kolab/var/horde/
-# chown kolab-n:kolab-n /kolab/var/horde/
-</pre>
-</li>
-<li>Under the 'Preference System' tab, select <code>LDAP</code> as the preferences driver, and enter the
-following values for each field (mirroring those specified under the 'Kolab' tab):<br />
-Base DN -> The same as Kolab\Base DN<br />
-DN of the root account -> The same as Kolab\Manager DN<br />
-Root DN password -> The same as Kolab\Manager Password<br />
-Username search key -> 'mail'
-</li>
-<li>Under the 'Mailer' tab, select <code>SMTP</code> as the mail send method.</li>
-<li>Under the 'Menu Settings' tab, check the 'Redirect to the Horde frameset after login' option.</li>
-</ul>
-</dd>
-
-
-</dl>
-
-<h4>Conclusion</h4>
-<p>*phew* That's it! You should now be able to log in to the webclient
-with any Kolab user. Quite a procedure to set it up, but I think you'll find it's worth it.
-We've put a lot of effort into the Webclient and as the current clients go,
-we'd like to think it's the best in terms of features :-) This guide is
-meant to tide users over until Horde releases their next stable version,
-at which time we can freeze the code and create an OpenPKG-compatible RPM
-that will greatly simplify this process of installing the webclient. Hang on
-till then!</p>
-
-<a name="opa"><h4>Appendix A</h4></a>
-
-<p>The OPA script; this should be put in your <code>~/.bashrc</code> or similar
-shell startup file.</p>
-
-<pre>
-opa () {
- root="$1"
- if [ ! -d $root ]; then
- echo "opa:ERROR: OpenPKG root directory $root not found"
- return 1
- fi
- if [ ! -f "$root/etc/rc" ]; then
- echo "opa:ERROR: does not contain OpenPKG hierarchy"
- return 1
- fi
- eval `$root/etc/rc --eval all env`
-}
-</pre>
-
-<a name="obmconf"><h4>Appendix B</h4></a>
-
-<p>This <code>obmtool.conf</code> file can be used to install a Horde-ready Kolab installation
-based on OpenPKG 2.0.</p>
-
-<pre>
-##
-## obmtool.conf -- OpenPKG poor man's Boot, Build & Management Tool Configuration
-## based on Ralf S. Engelschall's "obmtool.conf -- Development Tool Configuration"
-## Copyright (c) 2003 Thomas Lotterer <thomas at lotterer.net>
-##
-
-%common
- @hasfeature TAGFMT || exit # require obmtool to support TAGFMT
- TMPDIR=/ltmp # large tmp with 300MB space
- URL="ftp://ftp.zfos.org/brew/kolab/SRC" # used for non-ftp://ftp.openpkg.org/ packages
-
-%kolab
- echo "---- boot/build ${NODE} %${CMD} ----"
- PREFIX=/${CMD};
- loc='./' # '' (empty) for ftp.openpkg.org, '=' for URL, './' for CWD or absolute path
- pls=${loc:-+}
- with_genuine=no
-
- # start from scratch or upgrade within 2.0.x
- @install openpkg-2.0.0-2.0.0 \
- --tag="zfos" \
- --prefix="${PREFIX}" \
- --user="${CMD}" --group="${CMD}" \
- --muid="19414" --ruid="19415" --nuid="19416" \
- --mgid="19414" --rgid="19415" --ngid="19416"
- @install ${loc}make-3.80-2.0.0
- @install ${loc}binutils-2.14-2.0.0
- @install ${loc}gcc-3.3.3-2.0.0
- @install ${loc}fsl-1.4.0-2.0.0
- @install ${loc}mm-1.3.0-2.0.0
- @install ${loc}perl-5.8.3-2.0.0
- @install ${loc}perl-openpkg-5.8.3-2.0.0
- @install ${loc}perl-conv-5.8.3-2.0.0
- @install ${loc}readline-4.3.5-2.0.0
- @install ${loc}sharutils-4.2.1-2.0.0
- @install ${loc}ncurses-5.4.20040214-2.0.0
- @install ${loc}perl-term-5.8.3-2.0.0
- @install ${loc}perl-ds-5.8.3-2.0.0
- @install ${loc}perl-util-5.8.3-2.0.0
- @install ${loc}perl-mail-5.8.3-2.0.0
- @install ${loc}perl-crypto-5.8.3-2.0.0
- @install ${loc}perl-net-5.8.3-2.0.0
- @install ${loc}zlib-1.2.1-2.0.0
- @install ${loc}expat-1.95.7-2.0.0
- @install ${loc}perl-xml-5.8.3-2.0.0
- @install ${loc}perl-www-5.8.3-2.0.0
- @install ${loc}perl-time-5.8.3-2.0.0
- @install ${loc}openssl-0.9.7c-2.0.0
- @install ${loc}imap-2004rc6-2.0.0
- @install ${loc}perl-ssl-5.8.3-2.0.0
- @install ${loc}procmail-3.22-2.0.0
- @install ${loc}db-4.2.52.2-2.0.0
- @install ${loc}openldap-2.2.5-2.0.0
- @install ${loc}sasl-2.1.17-2.0.0 --with=ldap --with=login
- @install ${loc}getopt-20030307-2.0.0
- @install ${loc}proftpd-1.2.9-2.0.0 --with=ldap
- @install ${loc}pcre-4.5-2.0.0
- @install ${loc}gdbm-1.8.3-2.0.0
- @install ${pls}dbtool-1.6-2.0.0
- @install ${loc}postfix-2.0.18-2.0.0 --with=ldap --with=sasl --with=ssl
- @install ${loc}perl-sys-5.8.3-2.0.0
- @install ${loc}perl-ldap-5.8.3-2.0.0
- if [ ".${with_genuine}" = .no ]; then
- @install ${loc}perl-db-5.8.3-2.0.0
- @install ${pls}perl-kolab-5.8.3-2.0.0
- fi
- @install ${pls}imapd-2.2.3-2.0.0 --with=group
- @install ${loc}m4-1.4o-2.0.0
- @install ${loc}bison-1.35-2.0.0
- @install ${loc}flex-2.5.4a-2.0.0
- @install ${loc}libiconv-1.9.2-2.0.0
- @install ${loc}gettext-0.14.1-2.0.0
- #install ${loc}openpkg-tool-FIXME
- @install ${loc}patch-2.5.9-2.0.0
- @install ${loc}sed-4.0.9-2.0.0
- @install ${loc}libxml-2.6.6-2.0.0
- @install ${loc}libxslt-1.1.3-2.0.0
- @install ${loc}mysql-4.0.18-2.0.0
- @install ${loc}apache-1.3.29-2.0.0 \
- --with=mod_auth_ldap \
- --with=mod_dav \
- --with=mod_php \
- --with=mod_php_gdbm \
- --with=mod_php_gettext \
- --with=mod_php_imap \
- --with=mod_php_openldap \
- --with=mod_php_pear \
- --with=mod_php_xml \
- --with=mod_ssl \
- --with=mod_php_dom \
- --with=mod_php_mysql
- if [ ".${with_genuine}" = .no ]; then
- @install ${pls}kolab-20040217-2.0.0 --without=genuine
- else
- @install ${pls}kolab-20040217-2.0.0 --with=genuine
- fi
- @check
-
-%dump
- echo "PRG = \"$PRG\""
- echo "CMD = \"$CMD\""
- echo "URL = \"$URL\""
- echo "TRACK = \"$TRACK\""
- echo "EGREP = \"$EGREP\""
- echo "CHECKONLY = \"$CHECKONLY\""
- echo "ERASESURPLUS = \"$ERASESURPLUS\""
- echo "HASX11 = \"$HASX11\""
- echo "PREFIX = \"${PREFIX}\""
- echo "ARCH = \"${ARCH}\""
- echo "OS = \"${OS}\""
- echo "TAG = \"${TAG}\""
- echo "TMPDIR=\"${TMPDIR}\""
-</pre>
+<div class="note">
+Please report any development issues to the
+<a href="/mailman/listinfo/kolab-devel">Kolab development mailing list</a>.
+Please feel free to submit patches, documentation or anything else you can
+think of that would help the project.
+</div>
m4_include(footer.html.m4)
Index: default.css
===================================================================
RCS file: /kolabrepository/doc/www/src/default.css,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- default.css 7 Jun 2004 15:19:12 -0000 1.1
+++ default.css 10 Jun 2004 22:48:34 -0000 1.2
@@ -1,14 +1,31 @@
body {
- font: 8pt Verdana, Arial, Helvetica, sans-serif;
background: url('images/bg_lines.png');
}
+body, td {
+ font: 8pt Verdana, Arial, Helvetica, sans-serif;
+}
+
+dt {
+ font-weight: bold;
+}
+
+dd {
+ margin-bottom: 0.5em;
+}
+
img {
border: 0;
}
-.logo {
- text-align: center;
+div p {
+ margin-top: 0;
+}
+
+hr {
+ height: 2px;
+ border: 1px solid #555;
+ background-color: #555;
}
a:hover {
@@ -16,10 +33,70 @@
background: #ccf;
}
+code {
+ background-color: white;
+}
+
+thead {
+ background-color: #ddf;
+}
+
+.yes {
+ background-color: #cdffcd;
+}
+
+.part {
+ background-color: #ffffcd;
+}
+
+.no {
+ background-color: #ffcdcd;
+}
+
#logo {
text-align: center;
}
+#intro {
+ font-size: 110%;
+ font-style: italic;
+ text-indent: 2em;
+ margin: 2em;
+ /*margin-right: 300px;*/
+}
+
+#appendices {
+ list-style-type: upper-latin;
+}
+
+.toclnk {
+ text-align: center;
+ border: 1px dashed black;
+ float: right;
+ clear: none;
+ padding: 0.5em;
+ margin: 0.5em;
+ /*background-color: silver;*/
+}
+
+.hint {
+ font-style: italic;
+}
+
+.note {
+ border: 1px dashed blue;
+ padding: 0.5em;
+ background-color: #cdcdff;
+ margin: 0.5em;
+}
+
+.warning {
+ border: 1px dashed red;
+ padding: 0.5em;
+ background-color: #ffcdcd;
+ margin: 0.5em;
+}
+
/* Menu container */
#menu {
position: absolute;
@@ -34,7 +111,7 @@
font-weight: bold;
color: #fff;
text-align: left;
- padding-left: .5em;
+ padding-left: 0.5em;
white-space: nowrap;
margin-bottom: 0;
}
@@ -46,7 +123,7 @@
background: #fff;
margin-top: 0;
margin-bottom: 20px;
- padding: .5em;
+ padding: 0.5em;
}
/* Content container */
@@ -62,16 +139,17 @@
font-size: 200%;
font-weight: bold;
background: #ddf;
- padding-left: .5em;
- border-bottom: .5em solid #00d;
+ padding-left: 0.5em;
+ border-bottom: 0.5em solid #00d;
}
/* Content box body */
.cbox {
background: #eee;
- padding: .5em;
+ padding: 0.5em;
}
+/* Footer block */
#footer {
border-bottom: 2px solid #00d;
border-top: 2px solid #00d;
@@ -79,3 +157,69 @@
text-align: center;
background: #ddf;
}
+
+/* Last-updated timestamp tag */
+#date {
+ text-align: center;
+ font-size: 85%;
+ font-family: monospace;
+ /*border: 1px dashed black;*/
+ float: right;
+ clear: none;
+ padding-right: 0.5em;
+ padding-left: 0.5em;
+ background-color: white;
+ margin: 0.5em;
+}
+
+/* Indented section */
+.section {
+ margin-left: 2em;
+}
+
+/* Shell/source code */
+.shell {
+ border: 1px dashed black;
+ padding: 0.5em;
+ background-color: white;
+ margin: 0.5em;
+}
+
+/* Latest news item */
+.latestnews {
+ border: 1px dashed blue;
+ padding: 0.5em;
+ background-color: #cdcdff;
+ margin: 0.5em;
+}
+
+/* News date */
+.newsd {
+ font-size: 110%;
+ font-weight: bold;
+ white-space: nowrap;
+ width: 200px;
+}
+
+/* News header */
+.newsh {
+ font-size: 110%;
+ font-weight: bold;
+}
+
+/* News body */
+.newsb {
+ padding-left: 3em;
+}
+
+/* News item */
+.news {
+ border: 1px dashed black;
+ padding: 0.5em;
+ background-color: white;
+ margin: 0.5em;
+}
+
+.news .newsb {
+ margin-bottom: 2em;
+}
\ No newline at end of file
Index: documentation.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/documentation.html.m4,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- documentation.html.m4 1 Aug 2003 17:18:37 -0000 1.4
+++ documentation.html.m4 10 Jun 2004 22:48:34 -0000 1.5
@@ -1,24 +1,20 @@
m4_define(`PAGE_TITLE',`Documentation')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
-Documents on this page got published
-after conclusion of the Kroupware Project.
-<p>
-Currently most up to date version are still accessible from
-<a href="http://kroupware.org/documentation.html"
-><strong>the Kroupware documentation page</strong></a>.
+<p>Documents on this page were published after the conclusion of the Kroupware
+Project. Currently the most up to date versions are still accessible from the
+<a href="http://kroupware.org/documentation.html">Kroupware documentation page</a>.
+</p>
<h2>KDE Client Manual</h2>
<ul>
- <li>
- Version 0.9.x cvs20030801
- (Corresponding to client version 1.0rc2)
-
- <a href="doc/kde-client-manual-0.9cvs20030801-html/index.html">Browse Online</a> |
+ <li><b>Version 0.9.x cvs20030801</b>
+ (Corresponding to client version 1.0rc2)
+ <a href="doc/kde-client-manual-0.9cvs20030801-html/index.html">Browse Online</a> |
<a href="doc/kde-client-manual-0.9cvs20030801-html.zip">Download html groupware_de-1.0.1-html.zip</a>
| <a href="doc/kde-client-manual-0.9cvs20030801.pdf">Download pdf</a>
- <br>
+ <br />
<small>
(20030801)
</small>
Index: footer.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/footer.html.m4,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- footer.html.m4 10 Jun 2004 16:57:53 -0000 1.14
+++ footer.html.m4 10 Jun 2004 22:48:34 -0000 1.15
@@ -54,7 +54,9 @@
<a href="https://intevation.de/roundup/kolab/">Online Issue/Wish Tracker</a><br />
<br />
LINK(`howtos.html', `HOWTOs')
-<a href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/">Mini-Howtows in CVS</a>
+<a href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/">Mini-Howtows in CVS</a><br />
+<br />
+LINK(`client-features.html', `Client Feature Matrix')
</div>
<!-- DEVELOPERS -->
@@ -75,14 +77,22 @@
<br/>
<a href="/pipermail/kolab-commits/">Archive</a> |
<a href="/mailman/listinfo/kolab-commits">Subscribe/Manage</a>
-</small><br />
-<a href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/">Browse CVS</a>
-</small><br />
-<br />
+</small><br /><br />
LINK(`cvs-kolab.html', `Kolab Server Development')
+<a href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/">Browse CVS</a>
</div>
-<!-- EXISTS -->
+<!-- EXPERIMENTAL -->
+<div class="mbh">Experimental features</div>
+<div class="mbox">
+<b>NOTE: These features are considered EXPERIMENTAL and/or IN DEVELOPMENT and
+as such should NOT be used in production.</b><br /><br />
+<small>You may discuss any issues that you have with these features on the
+development mailing list.</small><br /><br />
+LINK(`webclient.html', `Kolab Webclient')
+</div>
+
+<!-- EXITS -->
<div class="mbh">Exits</div>
<div class="mbox">
<a href="http://kroupware.org/">Kroupware</a>
Index: howto-kolab-kde-client.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/howto-kolab-kde-client.html.m4,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- howto-kolab-kde-client.html.m4 29 Apr 2004 15:55:26 -0000 1.2
+++ howto-kolab-kde-client.html.m4 10 Jun 2004 22:48:34 -0000 1.3
@@ -1,6 +1,6 @@
m4_define(`PAGE_TITLE',`Install Kolab KDE Client')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
<p><em> The following instructions are aimed at the technical advanced
administrator.</em>
@@ -12,7 +12,7 @@
<p>The KDE kroupware client is KDE 3.1 based.
If you want to try the client as a user or developer, the
-3.1 based approach is the only way to run it.
+3.1 based approach is the only way to run it.
The situation for CVS HEAD is coordinated through the regular
KDE developer channels.
</p>
@@ -28,8 +28,8 @@
Of course <em>you need to have KDE 3.1</em> as released or from KDE_3_1_BRANCH.
Normal tarball build procedure is
<kbd>./configure --prefix=/to/your/path ;</kbd>
-<kbd>make ;</kbd>
-<kbd>make install</kbd>.
+<kbd>make ;</kbd>
+<kbd>make install</kbd>.
<h4>From CVS</h4>
<p>
@@ -82,7 +82,7 @@
TKDE_3_1_BRANCH.</p>
<p>
-Please report any issues to the public mailinglist
+Please report any issues to the public mailinglist
<a href="mailto:kolab-users at kolab.org">kolab-users at kolab.org</a>.
</p>
Index: howto-kolab.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/howto-kolab.html.m4,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- howto-kolab.html.m4 29 Apr 2004 15:55:26 -0000 1.2
+++ howto-kolab.html.m4 10 Jun 2004 22:48:34 -0000 1.3
@@ -1,6 +1,6 @@
m4_define(`PAGE_TITLE',`Install Kolab')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
m4_define(`LINK',`m4_ifelse($1, NO_LINK_FOR,`
»$2
@@ -12,13 +12,13 @@
<h3>Install current Kolab Server release</h3>
-You'll find the current (>=rc1) Kolab Server source releases
+You'll find the current (>=rc1) Kolab Server source releases
at:
<a href="ftp://ftp.kde.org/pub/kde/unstable/server/kolab"
><tt>ftp.kde.org/pub/kde/unstable/server/kolab</tt></a>.
<br>
-Please use one of the
+Please use one of the
<a href="http://www.kde.org/ftpmirrors.html"
>KDE ftp mirrors</a>
<p>
@@ -29,23 +29,23 @@
<p>
-Follow the Quick Installation Manual (QIM) and READMEs.
+Follow the Quick Installation Manual (QIM) and READMEs.
<br>
-Compare it to the lastest
+Compare it to the lastest
<a href="http://intevation.de/cgi-bin/viewcvs-kolab.cgi/server/doc/QIM?only_with_tag=KOLAB_1_0"
>QIMs from KOLAB_1_0 CVS-branch</a>.
<h3>Report results</h3>
<p>
-Please report any issues to the public mailinglist
+Please report any issues to the public mailinglist
<a href="mailto:kolab-users at kolab.org">kolab-users at kolab.org</a>.
<p>
<h3>Development versions via CVS</h3>
Interested developers can check out the
- LINK(`cvs-kolab.html', `Kolab Server Development')
+ LINK(`cvs-kolab.html', `Kolab Server Development')
page.<br>
Index: howtos.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/howtos.html.m4,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- howtos.html.m4 24 Jul 2003 06:16:59 -0000 1.3
+++ howtos.html.m4 10 Jun 2004 22:48:34 -0000 1.4
@@ -1,51 +1,42 @@
m4_define(`PAGE_TITLE',`HOWTOs')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
+
+<p class="hint">Have you done something cool with the Kolab server? Please
+share ;-) Articles or links can be sent to <a
+href="mailto:kolab at codefusion.co.za">kolab at codefusion.co.za</a> to be
+included in this page. Your submissions might even find their way into future
+releases of Kolab!</p>
-<em>Have you done something cool with the Kolab server?</em><br>
-<em>Please share ;-)</em>
<p>
Items of interest are:
<ul>
-<li>Samba Integration into the Kolab LDAP directory.
-</li>
-<li>Kolab High-Availability work (LDAP replication,etc.)
-</li>
-<li>Anti-Virus and Anti-Spam integration.
-</li>
-
+<li>Samba Integration into the Kolab LDAP directory.</li>
+<li>Kolab High-Availability work (LDAP replication,etc.)</li>
+<li>Anti-Virus and Anti-Spam integration.</li>
</ul>
-
-Articles or links can be sent to
-<a href="mailto:kolab at codefusion.co.za">kolab at codefusion.co.za</a>
- to be included in this page.
-
-</p>
-<p>
-Some of these submissions might even find themselves into the latest releases of Kolab!
</p>
<h2>HOWTO Kolab+Amavisd-new+Spam Assassin+Sophos</h2>
<ul>
- <li>
- Version 1.2
+ <li><b>Version 1.2</b>
<a href="howtos/amavis_spamassassin_sophos/amavis_spamassassin_sophie.pdf">Download pdf</a> |
<a href="howtos/amavis_spamassassin_sophos/amavis_spamassassin_sophie.sxw">Download OpenOffice.org doc</a> |
- <a href="howtos/amavis_spamassassin_sophos/amavis_spamassassin_sophie_scripts.tgz">Resource Files</a> |
- <br>
+ <a href="howtos/amavis_spamassassin_sophos/amavis_spamassassin_sophie_scripts.tgz">Resource Files</a>
+ <br />
<small>
(20030724)
</small>
</li>
</ul>
+
<h2>HOWTO Kolab+Amavisd-new+Spam Assassin+Clam</h2>
<ul>
- <li>
- Version 1.0
+ <li><b>Version 1.0</b>
<a href="howtos/amavis_spamassassin_clam/amavis_spamassassin_clam.pdf">Download pdf</a> |
<a href="howtos/amavis_spamassassin_clam/amavis_spamassassin_clam.sxw">Download OpenOffice.org doc</a> |
- <a href="howtos/amavis_spamassassin_clam/amavis_spamassassin_clam_scripts.tgz">Resource Files</a> |
- <br>
+ <a href="howtos/amavis_spamassassin_clam/amavis_spamassassin_clam_scripts.tgz">Resource Files</a>
+ <br />
<small>
(20030724)
</small>
Index: index.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/index.html.m4,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- index.html.m4 7 Jun 2004 15:48:29 -0000 1.22
+++ index.html.m4 10 Jun 2004 22:48:34 -0000 1.23
@@ -1,47 +1,165 @@
m4_define(`PAGE_TITLE', `Home')
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
-<p>
+<p id="intro">
The goal of the Kolab Project is to maintain and enhance
a Free Software groupware solution called Kolab.
It builds on software and concepts developed during the
<a href="http://kroupware.org/">Kroupware Project</a>,
in particular the Kolab Server and KDE Kroupware Client.
+</p>
-<h3>News</h3>
-<strong>
-May 28th, 2004:
-<a href="http://www.citadel.org/kolab.php"
->Citadel as Kolab1 server.</a>
-</strong>
-Freebusy handling, directory server architecure
-and lack of legacy support make it slightly different,
-but Citatel/UX v6.21 was fully tested with KDE Kolab1 Clients.
-<br>
-May 10th, 2004:
-<a href="http://kolab.org/pipermail/kolab-announce/2004/000003.html"
->Security advisory for Kolab Server.</a>
-<br>
-April, 2004: <a href="/cvs-kolab.html">Kolab Web Client</a> (in development) has been updated.
-<br>
-April, 2004: <a href="/pipermail/kolab-users/2004-April/000092.html">Kolab2 plans</a> are emerging.
-<br>
-March, 2004: <a href="/mailman/listinfo/kolab-users">Kolab-users mailing list</a> launched.
-<br>
-January, 2004: <a href="http://www.thekompany.com/projects/aethera/" name="Aethera">Aethera</a> now supports Kolab.
-<br>
-December 1, 2003: <a href="https://intevation.de/roundup/kolab/">Kolab Issue/Wish Tracker</a> launched.
-<br>
-October 16, 2003: <a href="http://eforum.de/">Kolab Wishes Forum</a> launched.
-<br>
-August 5, 2003: Wanted Feature: Multiple domains -
-<a href="http://lists.kde.org/?l=kroupware&m=105999548707438&w=2"
->call for shared funding posted to the list.</a>
-<br>
-July 25th, 2003: Kroupware Pressrelease:
-<a href="http://kroupware.org/news/pr-20030725.html"
->Kroupware Project finished -- Kolab emerges</a>
+<h2>News</h2>
+
+<!-- BEGIN LATEST BLOCK -->
+<div class="latestnews">
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">May 28th, 2004</td>
+<td class="newsh">»
+ <a href="http://www.citadel.org/kolab.php">
+ Citadel as Kolab1 server.</a>
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ Freebusy handling, directory server architecure
+ and lack of legacy support make it slightly different,
+ but Citatel/UX v6.21 was fully tested with KDE Kolab1 Clients.
+</div>
+
+</div>
+<!-- END LATEST BLOCK -->
+
+<!-- BEGIN NEWS BLOCK -->
+<div class="news">
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">May 10th, 2004</td>
+<td class="newsh">»
+ <a href="http://kolab.org/pipermail/kolab-announce/2004/000003.html"
+ >Security advisory for Kolab Server.</a>
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ A new security advisory for the Kolab server is available. Users are urged
+ to update as soon as possible.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">April, 2004</td>
+<td class="newsh">»
+ <a href="cvs-kolab.html">Kolab Web Client</a>
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ The currently in-development Kolab Webclient has been updated with several
+ new features.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">April, 2004</td>
+<td class="newsh">»
+ <a href="/pipermail/kolab-users/2004-April/000092.html">Kolab2 plans</a>
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ Kolab2 development has kicked off. Join the development list if you would
+ like to be a part of shaping the next generation Kolab server.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">March, 2004</td>
+<td class="newsh">»
+ <a href="/mailman/listinfo/kolab-users">Kolab-users mailing list</a> launched
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ A new list catering to Kolab users has been launched. Users of the server
+ are encouraged to join the list for help with the installation and running
+ of the Kolab server.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">January, 2004</td>
+<td class="newsh">»
+ <a href="http://www.thekompany.com/projects/aethera/" name="Aethera">Aethera</a> now supports Kolab.
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ The Aethera cross-platform groupware client now has support for the Kolab
+ server as a groupware backend.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">December 1, 2003</td>
+<td class="newsh">»
+ <a href="https://intevation.de/roundup/kolab/">Kolab Issue/Wish Tracker</a> launched
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ An issue tracker has been lauched to handle bug and feature request tracking
+ for the Kolab server. Users are encouraged to submit bug reports for any
+ issues they may encounter to the tracker in aid the developers with bug
+ fixing.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">October 16, 2003</td>
+<td class="newsh">»
+ <a href="http://eforum.de/">Kolab Forum</a> launched
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ A forums for general discussion of the Kolab server has been lauched as an
+ alternative to the mailing lists.
+</div>
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">August 5, 2003</td>
+<td class="newsh">»
+ Wanted Feature: Multiple domains
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ A <a href="http://lists.kde.org/?l=kroupware&m=105999548707438&w=2"
+ >call for shared funding</a> has posted to the list in order to speed up
+ development of this useful feature.
+</div>
+
+<!-- HEADER LINE -->
+<table>
+<tr><td class="newsd">July 25th, 2003</td>
+<td class="newsh">»
+ Kroupware Pressrelease
+</td></tr>
+</table>
+<!-- ITEM BODY -->
+<div class="newsb">
+ The <a href="http://kroupware.org/news/pr-20030725.html"
+ >Kroupware Project has been completed</a>, and as a result Kolab has emerged.
+</div>
+
+</div>
+<!-- END NEWS BLOCK -->
<h3>Kolab Clients</h3>
<ul>
@@ -108,9 +226,13 @@
<br><br>
<ul>
<li><em>Horde Webmail</em><br>
-Currently part of Kolab CVS, this is still under development. It will allow users to access their server
-mailboxes and have full groupware functionality available. If you would like to contribute join the
-<a href="/mailman/listinfo/kolab-devel">kolab-devel mailing list</a>. All contributions welcome.
+Currently part of <a href="http://www.horde.org">Horde</a> CVS, this is still
+under development. It will allow users to access their server mailboxes and
+have full groupware functionality available. If you would like to contribute
+join the <a href="/mailman/listinfo/kolab-devel">kolab-devel
+mailing list</a>. All contributions welcome.<br><br>
+Instructions on how to obtain and install the webclient can be found
+<a href="webclient.html">here</a>.
</li>
<br>
<li><em>Kontact (KDE HEAD)</em><br>
Index: kolab-plugins.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/kolab-plugins.html.m4,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- kolab-plugins.html.m4 26 Mar 2004 18:38:21 -0000 1.7
+++ kolab-plugins.html.m4 10 Jun 2004 22:48:34 -0000 1.8
@@ -1,6 +1,6 @@
m4_define(`PAGE_TITLE',`Outlook Plugins for Accessing Kolab Servers')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
<em>Note that all stable Plugins at time of writing
will make Outlook save E-Mails over dIMAP containing TNEF with MAPI BLOB
@@ -20,7 +20,7 @@
<li><b>(SourceXtreme's mapi connector)</b><br>
Planned License: <em>Free Software</em><br>
<a href="http://sourcextreme.com/">Ian Geiser's Company SourceXtreme</a>
-is working on a mapi connector.
+is working on a mapi connector.
First development release expected spring 2004.
<li><b>Konsec Konnektor</b> (<a href="http://www.konsec.com/">www.konsec.com</a>) <br>
Index: screenshots.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/screenshots.html.m4,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- screenshots.html.m4 12 Jun 2003 18:51:04 -0000 1.1
+++ screenshots.html.m4 10 Jun 2004 22:48:34 -0000 1.2
@@ -1,64 +1,66 @@
m4_define(`PAGE_TITLE',`Screenshot Gallery')
-
m4_include(header.html.m4)
+<div id="date">This page was updated on:<br />$Date$</div>
-Not necessarily showing the latest versions of the software.
+<p><b>NOTE</b>: These screenshots do not necessarily show the latest
+versions of the software, and as such should not be taken as indication of the
+quality of the current software.</p>
<h2>KDE Kolab Client</h2>
-<table cellpadding=14 bgcolor=white>
-<tr valign=bottom>
-<td>
+<table cellpadding="14" bgcolor="white" width="100%">
+<tr valign="bottom">
+<td align="center">
<a href="images/shot-kde-client-calendar1.png"
><img src="images/shot-kde-client-calendar1.small.png" width=200 height=145
- border=0 ><br>Calender View (790x625 50 kByte)</a>
+ border=0 ><br /><br />Calender View (790x625 50 kByte)</a>
</td>
-<td>
+<td align="center">
<a href="images/shot-kde-client-edit-contact1.png"
><img src="images/shot-kde-client-edit-contact1.small.png" width=200 height=138
- border=0 ><br>Contact edit dialog (711x498 44 kByte)</a>
+ border=0 ><br /><br />Contact edit dialog (711x498 44 kByte)</a>
</td>
-<tr valign=bottom>
-<td>
+<tr valign="bottom">
+<td align="center">
<a href="images/shot-kde-client-edit-event1.png"
><img src="images/shot-kde-client-edit-event1.small.png" width=200 height=97
- border=0 ><br>Invite to an event (854x700 44 kByte)</a>
+ border=0 ><br /><br />Invite to an event (854x700 44 kByte)</a>
</td>
-<td>
+<td align="center">
<a href="images/shot-kde-client-edit-task1.png"
><img src="images/shot-kde-client-edit-task1.small.png" width=200 height=124
- border=0 ><br>Edit a task (845x770 67 kByte)</a>
+ border=0 ><br /><br />Edit a task (845x770 67 kByte)</a>
</td>
-<tr valign=bottom>
-<td>
+<tr valign="bottom">
+<td align="center">
<a href="images/shot-kde-client-notes1.png"
><img src="images/shot-kde-client-notes1.small.png" width=200 height=123
- border=0 ><br>Kmail viewing Notes(858x618 66 kByte)</a>
+ border=0 ><br /><br />Kmail viewing Notes(858x618 66 kByte)</a>
</td>
</table>
<h2>Kolab Server Web-Admin-Interface</h2>
-<table cellpadding=14 bgcolor=white>
-<tr valign=bottom>
-<td>
+<table cellpadding="14" bgcolor="white" width="100%">
+<tr valign="bottom">
+<td align="center">
<a href="images/shot-web-admin-users1.png"
><img src="images/shot-web-admin-users1.small.png" width=200 height=107
- border=0 ><br>Maintaining users(686x628 72 kByte)</a>
+ border=0 ><br /><br />Maintaining users(686x628 72 kByte)</a>
</td>
-<td>
+<td align="center">
<a href="images/shot-web-services1.png"
><img src="images/shot-web-services1.small.png" width=200 height=85
- border=0 ><br>Administrate running services(779x698 61 kByte)</a>
+ border=0 ><br /><br />Administrate running services(779x698 61 kByte)</a>
</td>
-<tr valign=bottom>
-<td>
+<tr valign="bottom">
+<td align="center">
<a href="images/shot-web-user-settings1.png"
><img src="images/shot-web-user-settings1.small.png" width=200 height=99
- border=0 ><br>My User Settings(658x705 62 kByte)</a>
+ border=0 ><br /><br />My User Settings(658x705 62 kByte)</a>
</td>
</table>
Index: webclient.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/webclient.html.m4,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- webclient.html.m4 10 Jun 2004 18:58:55 -0000 1.1
+++ webclient.html.m4 10 Jun 2004 22:48:34 -0000 1.2
@@ -1,13 +1,41 @@
m4_define(`PAGE_TITLE', `Webclient')
m4_include(header.html.m4)
-<div id="date">Page updated at $Date$</div>
+<div id="date">This page was updated on:<br />$Date$</div>
<p class="hint">Please direct any comments and suggestions about this guide to
<a href="mailto:s.binge at codefusion.co.za">Stuart Bingë</a></p>
<hr />
-<h3>Highlights of the current webclient release:</h3>
+<a name="toc"><h2>Table of Contents</h2></a>
+<ol>
+<li><a href="#highlights">Highlights of the current webclient release</a></li>
+<li><a href="#warning">A word of warning before you begin</a></li>
+<li><a href="#prereqs">Prerequisites to installing the webclient</a></li>
+<li><a href="#step0">Initial step: ensure your Kolab environment is ready</a></li>
+<li><a href="#phpa">Optional Step: Install a PHP Accelerator</a></li>
+<li><a href="#step1">Step 1: Download and install the necessary PEAR packages</a></li>
+<li><a href="#step2">Step 2: Check out the necessary Horde modules</a></li>
+<li><a href="#step3">Step 3: Install the Horde framework</a></li>
+<li><a href="#step4">Step 4: Copy the initial configuration files</a></li>
+<li><a href="#step5">Step 5: Edit the necessary configuration files</a></li>
+<li><a href="#step6">Step 6: Move Horde to its final location</a></li>
+<li><a href="#step7">Step 7: Setup OpenLDAP to accommodate Horde preferences</a></li>
+<li><a href="#step8">Step 8: Setup MySQL to accommodate the Horde datastore</a></li>
+<li><a href="#step9">Step 9: Configure the Horde applications</a></li>
+<li><a href="#concl">Conclusion</a></li>
+</ol>
+<ol id="appendices">
+<li><a href="#opa">Appendix A: The <code>opa</code> script</a></li>
+<li><a href="#obmconf">Appendix B: Horde-capable <code>obmtool.conf</code> file</a></li>
+</ol>
+
+<hr />
+
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="highlights"><h2>1. Highlights of the current webclient release</h2></a>
+
+<div class="section">
<dl>
<dt>Multiple calendars, notepads and tasklists</dt>
<dd>Each calendar, notepad and tasklist is stored in a separate IMAP
@@ -48,136 +76,165 @@
corrected within days of surfacing, meaning functionality remains at
peak levels.</dd>
</dl>
+</div>
-<div class="note">PLEASE NOTE: The Webclient, while technically
+<hr />
+
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="warning"><h2>2. A word of warning before you begin</h2></a>
+
+<div class="section">
+<div class="warning"><p><b>PLEASE NOTE:</b> The webclient, while technically
feature-complete, is still considered development quality. As such it is not
recommended that you run it in a production environment, however any and all
-potential testers are most welcome. There are most probably a whole host of
-bugs left in the code, and a lot of improvements can still be made, however
-as it stands it is a very usable product.</div>
+potential testers are most welcome. There are probably a whole host of bugs
+left in the code, and a lot of improvements can still be made, however
+as it stands it is a very usable product.</p>
-<p>Also note
-that while this is considered the 'Kolab Webclient', it is still based on an
-existing project (the <a href="http://www.horde.org/">Horde</a> project), and
-as the current Webclient codebase is contained in Horde's CVS repository it relies
-an an underlying code base that is also under constant development. What this
-boils down to is any bugs that you may encounter might not necessarily be related
-the the Kolab Webclient portion of the code, but instead be within the Horde code
-itself.</p>
+</p>Also note that while this is considered the 'Kolab Webclient', it is
+still based on an existing project, namely the excellent
+<a href="http://www.horde.org/">Horde</a> project. As the current webclient
+code is housed in the Horde CVS repository it therefore relies an an
+underlying code base that is also under constant development. What this boils
+down to is any bugs that you encounter might not necessarily be related to
+the Kolab Webclient portion of the code, but instead the Horde code itself.</p>
+</div>
-<p>Currently the Webclient does not interoperate with the Kolab KDE Client, nor
-any Outlook-configured mailboxes, so any users that are to use the Webclient should
-do so exclusively. Interoperability is most definitely one of the upcoming features
-you can look forward to - even between Outlook mailboxes and the Webclient.</p>
+<p>Currently the Webclient does not interoperate with the Kolab KDE Client,
+nor any Outlook-configured mailboxes, so any users that are to use the
+Webclient should do so exclusively. Interoperability is most definitely one
+of the upcoming features you can look forward to - even between Outlook
+mailboxes and the Webclient.</p>
<p>Any commentary about the Webclient should be directed either to the
<a href="http://lists.horde.org/mailman/listinfo/dev">Horde development list</a>
-or to the <a href="http://kolab.org/mailman/listinfo/kolab-devel">Kolab development list
-</a>. We should pick up discussion on either.</p>
-
-<p>This guide assumes you will be running Horde & Kolab on the same machine.
-It should technically be possible to separate the two; however, as of yet this
-has not been attempted. If you manage to do this we would greatly appreciate
-feedback as to how you did it, and we'll include it in this guide.</p>
-
-<p>This guide also assumes that your kolab installation is in <code>/kolab</code>
-- if it's not then just substitute in your specific kolab root location wherever
-you see the directory <code>/kolab</code> in this document.</p>
+or to the <a href="http://kolab.org/mailman/listinfo/kolab-devel">Kolab
+development list</a>. We should pick up discussion on either.</p>
+</div>
-<p>The following conventions are used, and assumptions made, in this document:
-<ul>
-<li>Commands that should be entered at the shell are preceded by hashes (<code>#</code>).</li>
+<hr />
-<li>You will be installing the Webclient as the root user.</li>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="prereqs"><h2>3. Prerequisites to installing the webclient</h2></a>
-<li>You installed Kolab through the <a href="http://www.zfos.org/">ZfOS</a> OBMTOOL
-method.</li>
+<div class="section">
+<p>This guide assumes you will be running Horde & Kolab on the same
+machine. It should technically be possible to separate the two; however, as
+of yet this has not been attempted. If you manage to do this we would greatly
+appreciate feedback as to how you did it, and we'll include it in this guide.
+It is also assumed that you will be installing the webclient as the root user.
+</p>
-<li>You are working in the Kolab environment while installing the Webclient
-(e.g. by running <code><a href="#opa">opa</a> /kolab</code>).</li>
+<p>This guide assumes that your kolab installation is in <code>/kolab</code>
+- if it is not then just substitute in your specific Kolab root location
+wherever you see the directory <code>/kolab</code> in this document. You
+should also be working in the Kolab environment while installing the
+Webclient (e.g. by running <code><a href="#opa">opa</a> /kolab</code>).</p>
-<li>You should create a temporary directory for use in the initial setup
-steps, while the necessary packages are being downloaded - the files should
+<p>You should create a temporary directory for use in the initial setup
+steps, while the necessary packages are being prepared - the files should
only be moved to their final locations once everything is in place. Once
-everything is installed you can remove this temporary directory; in this
-guide <code>/tmp</code> is used as the temporary location.</li>
+everything is installed you can remove all the files you placed in the
+temporary directory; in this guide <code>/tmp</code> is used as the
+temporary location.</p>
-<li>It is recommended that you put the following in your root users' <code>~/.cvsrc</code>:
-<pre>
-cvs -z3
-update -d -P
+<p>While not strictly necessary, it is recommended that you install your
+Kolab server via the <a href="http://www.zfos.org/">ZfOS</a> OBMTOOL method.
+This guide assumes that this is the case; if you installed the standard Kolab
+distribution then you will have to adapt as you progress through the document,
+and build any additional packages manually.</p>
+
+<p>It is recommended that you put the following in your root users'
+<code>~/.cvsrc</code> file:
+<pre class="shell">
+cvs -z4 -q
+update -dP
checkout -P
-diff -u
+diff -u3 -p
</pre>
-</li>
-</ul>
</p>
-<h4>Pre-installation</h4>
-<p>First of all you need to ensure your Kolab distribution is able to run Horde.
-This means installing additional OpenPKG RPMs and recompiling your Apache RPM
-with additional flags. You can obtain source RPMs from the <a
-href="ftp://ftp.openpkg.org/release/2.0/SRC/">OpenPKG 2.0 Source Repository</a>, or
-if you'd prefer and are running Kolab on an OpenPKG-supported platform, you
-can obtain binary RPMs from the <a href="ftp://ftp.openpkg.org/release/2.0/BIN">
-OpenPKG 2.0 Binary Repository</a></p>
+<p>In the following text commands that should be entered at the shell are
+preceded by hashes (<code>#</code>).</p>
+</div>
-<p>The necessary packages are:</p>
+<hr />
-<pre>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step0"><h2>4. Initial step: ensure your Kolab environment is ready</h2></a>
+
+<div class="section">
+<p>First of all you need to ensure your Kolab distribution is able to run
+Horde. This means installing additional OpenPKG RPMs and recompiling your
+Apache RPM with additional flags. You can obtain source RPMs from the <a
+href="ftp://ftp.openpkg.org/release/2.0/SRC/">OpenPKG 2.0 Source
+Repository</a>, or if you'd prefer and are running Kolab on an
+OpenPKG-supported platform, you can obtain binary RPMs from the
+<a href="ftp://ftp.openpkg.org/release/2.0/BIN">OpenPKG 2.0 Binary
+Repository</a>.</p>
+
+<p>The necessary packages are:
+<pre class="shell">
libxml-2.6.6-2.0.0
libxslt-1.1.3-2.0.0
mysql-4.0.18-2.0.0
</pre>
+</p>
-<p>Apache needs to be re-compiled with the following additional flags:</p>
-
-<pre>
+<p>Apache needs to be re-compiled with the following additional flags:
+<pre class="shell">
--with=mod_php_dom
--with=mod_php_mysql
</pre>
-
-<p>For your convenience I've included an updated Kolab/OpenPKG 2.0 obmtool.conf in
-<a href="#obmconf">Appendix B</a> that can be used to set up a Horde-capable Kolab
-installation.
</p>
-<p>Be sure to change your MySQL root password to something secure after installing
-MySQL. You can do this by running the following command:<p>
+<p>For your convenience I've included an updated Kolab/OpenPKG 2.0
+<code>obmtool.conf</code> in <a href="#obmconf">Appendix B</a> that can be
+used to set up a Horde-capable Kolab installation.</p>
-<pre>
+<div class="note">
+Be sure to change your MySQL root password to something secure after installing
+MySQL. You can do this by running the following command:
+
+<pre class="shell">
# mysqladmin -u root password "your-mysql-root-pw"
</pre>
+</div>
+</div>
-<h4>Optional Step</h4>
-<p>Install a PHP Accelerator.</p>
+<hr />
-<p>This step is not critical to get Horde running, however it is highly recommended
-if you want to have as responsive a Webclient as possible. This guide instructs on
-how to install the <a href="http://www.phpaccelerator.co.uk/">ionCube PHP Accelerator</a>,
-as it is exceptionally simple to set up and provides a very noticeable performance boost.
-If you prefer other accelerators and are able to get them to work with Kolab then please
-send instructions on how to install them and we'll put it up here.</p>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="phpa"><h2>5. Optional Step: Install a PHP Accelerator</h2></a>
+
+<div class="section">
+<p>This step is not critical to get Horde running, however it is highly
+recommended if you want to have as responsive a Webclient as possible. This
+guide instructs on how to install the
+<a href="http://www.phpaccelerator.co.uk/">ionCube PHP Accelerator</a>, as it
+is exceptionally simple to set up and provides a very noticeable performance
+boost. If you prefer other accelerators and are able to get them to work with
+Kolab then please send instructions on how to install them and we'll put it
+up here.</p>
<p>Download the relevant package for your platform and PHP version from the
-<a href="http://www.phpaccelerator.co.uk/download.php">ionCube Downloads Page</a>. As of
-time of writing for x86 Linux, this would be
-<a href="http://www.phpaccelerator.co.uk/releases/linux_i686-glibc2.1.3/1.3.3r2_4.3.0/php_accelerator-1.3.3r2_php-4.3.0_linux_i686-glibc2.1.3.tgz">1.3.3r2</a>
-for PHP version 4.3.0. You should read the INSTALL and CONFIGURATION files that are
-distributed with PHPA for details on how to fine-tune performance. If you just want to
-quickly set up an accelerated environment for use with Horde then the following commands
-should be suitable:</p>
+<a href="http://www.phpaccelerator.co.uk/download.php">ionCube Downloads
+Page</a>. As of time of writing for PHP version 4.3.0 running on x86 Linux,
+this would be <a href="http://www.phpaccelerator.co.uk/releases/linux_i686-glibc2.1.3/1.3.3r2_4.3.0/php_accelerator-1.3.3r2_php-4.3.0_linux_i686-glibc2.1.3.tgz">1.3.3r2</a>.You should read the <code>INSTALL</code> and <code>CONFIGURATION</code> files
+that are distributed with PHPA for details on how to fine-tune performance.
+If you just want to quickly set up an accelerated environment for use with
+Horde then the following commands should be suitable:</p>
-<pre>
+<pre class="shell">
# cd /tmp
# tar -xvzf php_accelerator*.tgz
# mv php_accelerator*/php_accelerator*.so /kolab/lib
# chown kolab:kolab /kolab/lib/php_accelerator*.so
</pre>
-<p>The following then needs to be added to <code>/kolab/etc/kolab/php.ini.template</code>:
-
-<pre>
+<p>The following then needs to be added to
+<code>/kolab/etc/kolab/php.ini.template</code>:
+<pre class="shell">
; PHP Accelerator extension
zend_extension="/kolab/lib/php_accelerator_1.3.3r2.so"
@@ -185,41 +242,55 @@
; optimal for a project as large as Horde.
phpa.shm_size = 16
</pre>
+</p>
-<p>It is also recommended that you increase the value of <code>memory_limit</code> in
-<code>/kolab/etc/kolab/php.ini.template</code> to 12M or even 16M, for optimal use with
-Horde.</p>
-
-<p>After saving <code>/kolab/etc/kolab/php.ini.template</code> run <code>kolabconf</code>
-to re-generate <code>php.ini</code> and restart the Apache server. You can test to see if
-the extension is operational by viewing the following script through your Kolab web server.</p>
+<p>It is also recommended that you increase the value of
+<code>memory_limit</code> in <code>/kolab/etc/kolab/php.ini.template</code>
+to <code>12M</code> or even <code>16M</code>, for optimal use with Horde.</p>
-<pre>
+<p>After saving <code>/kolab/etc/kolab/php.ini.template</code> run
+<code>kolabconf</code> to re-generate <code>php.ini</code> and restart the
+Apache server. You can test to see if the extension is operational by viewing
+the following script through your Kolab web server:
+<pre class="shell">
<?php phpinfo(); ?>
</pre>
+</p>
-<p>You should see something similar to the following after the initial version information:</p>
-
-<pre>
+<p>You should see something similar to the following after the initial
+version information:
+<pre class="shell">
This program makes use of the Zend Scripting Language Engine:
Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies
with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002,
by Nick Lindridge
</pre>
+</p>
-<p>PHP Accelerator is now installed. Any PHP script viewed through your Kolab webserver will
-have its bytecode cached by PHPA - note that if you are experiencing 'weirdness' when it
-comes to viewing in-development scripts (for example, your changes are not coming through
-or incorrect errors are being generated) then your PHPA cache may need to be refreshed.
-The easiest way to do this is to just stop Apache and <code>rm /tmp/phpa*</code>.</p>
+<p>PHP Accelerator is now installed. Any PHP script viewed through your Kolab
+webserver will have its bytecode cached by PHPA - note that if you are
+experiencing 'weirdness' when it comes to viewing in-development scripts (for
+example, your changes are not coming through or incorrect errors are being
+generated) then your PHPA cache may need to be refreshed. The easiest way to
+do this is to do the following:
+<pre class="shell">
+# /kolab/etc/rc apache stop
+# rm /tmp/phpa*
+# /kolab/etc/rc apache start
+</pre>
+</p>
-<p>Now then, on to the actual Webclient installation instructions.</p>
+<p>Now then, on to the actual webclient installation instructions.</p>
+</div>
-<h4>Step 1</h4>
-<p>Download and install the necessary PEAR packages.</p>
+<hr />
-<p>1. Horde's PEAR distribution:</p>
-<pre>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step1"><h2>6. Step 1: Download and install the necessary PEAR packages</h2></a>
+
+<div class="section">
+<p>1. Horde's PEAR distribution:
+<pre class="shell">
# cd /tmp
# wget ftp://ftp.horde.org/pub/pear/pear-1.3.tar.bz2
# tar xvjf pear-1.3.tar.bz2
@@ -227,46 +298,72 @@
# rm pearcmd.php
# cp -R * /kolab/lib/php/
</pre>
+</p>
<p>2. Miscellaneous PEAR packages from PEAR CVS (Instructions from
-<a href="http://www.php.net/anoncvs.php">http://www.php.net/anoncvs.php</a>)</p>
-
-<pre>
+<a href="http://www.php.net/anoncvs.php">http://www.php.net/anoncvs.php</a>):
+<pre class="shell">
# cd /tmp
# cvs -d :pserver:cvsread at cvs.php.net:/repository login
</pre>
-<p>(When asked for a password, use 'phpfi').</p>
-<pre>
+(When asked for a password, use 'phpfi').
+<pre class="shell">
# cvs -d :pserver:cvsread at cvs.php.net:/repository checkout pear/HTTP_WebDAV_Client
# pear install pear/HTTP_WebDAV_Client/package.xml
</pre>
+</p>
+</div>
-<h4>Step 2</h4>
-<p>Check out the necessary Horde modules from Horde's CVS (instructions from
-<a href="http://www.horde.org/source/using.php">http://www.horde.org/source/using.php</a>):</p>
+<hr />
-<pre>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step2"><h2>7. Step 2: Check out the necessary Horde modules</h2></a>
+
+<div class="section">
+<p>Check out the necessary Horde modules from Horde's CVS (instructions from
+<a href="http://www.horde.org/source/using.php">http://www.horde.org/source/using.php</a>):
+<pre class="shell">
# cd /tmp
# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository login
</pre>
-<p>(When asked for a password, use 'horde').</p>
-<pre>
+(When asked for a password, use 'horde').
+<pre class="shell">
# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository checkout horde framework imp kronolith mnemo nag passwd turba ingo
+</pre>
+Optional: remove the extraneous CVS directories:
+<pre class="shell">
# find . -type d -name CVS | xargs rm -rf
</pre>
+</p>
+</div>
-<h4>Step 3</h4>
-<p>Install the Horde framework:</p>
+<hr />
-<pre>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step3"><h2>8. Step 3: Install the Horde framework</h2></a>
+
+<div class="section">
+<p>Install the Horde framework:
+<pre class="shell">
# cd /tmp/framework
# php install-packages.php
</pre>
+Optional: remove the framework directory:
+<pre class="shell">
+# cd /tmp
+# rm -rf framework
+</pre>
+</p>
+</div>
-<h4>Step 4</h4>
-<p>Move the default Horde configuration files to their final locations:</p>
+<hr />
-<pre>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step4"><h2>9. Step 4: Copy the initial configuration files</h2></a>
+
+<div class="section">
+<p>Move the default Horde configuration files to their final locations:
+<pre class="shell">
# cd /tmp
# mv horde/config/conf.php.dist horde/config/conf.php
# mv horde/config/prefs.php.dist horde/config/prefs.php
@@ -293,9 +390,15 @@
# mv turba/config/attributes.php.dist turba/config/attributes.php
# mv turba/config/sources.php.dist turba/config/sources.php
</pre>
+</p>
+</div>
-<h4>Step 5</h4>
+<hr />
+
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step5"><h2>10. Step 5: Edit the necessary configuration files</h2></a>
+<div class="section">
<p>Some Horde configuration files need to be edited by hand; the rest
can be auto-generated through the Horde Admin interface. You may want
to <code>chmod 0600</code> these files for additional security. The files
@@ -332,169 +435,218 @@
<code>$backends['kolab_global']</code> and <code>$backends['kolab_local']</code>
definitions (should both be the last two entries in the file).</dd>
</dl>
+</div>
-<h4>Step 6</h4>
+<hr />
+
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step6"><h2>11. Step 6: Move Horde to its final location</h2></a>
+
+<div class="section">
<p>Move the horde directories to their final location. Note that you can put
the Webclient in whatever directory you want and link to it from your
Kolab WWW directory, however in this document we just move the Horde
-directories directly into the WWW directory.</p>
-
-<pre>
+directories directly into the WWW directory.
+<pre class="shell">
# cd /tmp
-# chown -R kolab-n:kolab-n horde framework imp kronolith mnemo nag passwd turba ingo
+# chown -R kolab-n:kolab-n horde imp kronolith mnemo nag passwd turba ingo
# mv horde /kolab/var/kolab/www/
# mv imp kronolith mnemo nag passwd turba ingo /kolab/var/kolab/www/horde/
</pre>
+</p>
+</div>
-<h4>Step 7</h4>
+<hr />
-<p>Install the Horde schema into OpenLDAP. This schema allows Horde preferences
-to be stored in each Kolab user's object within LDAP. Add the following to your
-<code>/kolab/etc/kolab/slapd.conf.template</code> after the existing
-schema include lines:</p>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step7"><h2>12. Step 7: Setup OpenLDAP to accommodate Horde preferences</h2></a>
-<pre>
+<div class="section">
+<p>Install the Horde schema into OpenLDAP. This schema allows Horde
+preferences to be stored in each Kolab user's object within LDAP. Add the
+following to your <code>/kolab/etc/kolab/slapd.conf.template</code> after
+the existing schema include lines:
+<pre class="shell">
include /kolab/var/kolab/www/horde/scripts/ldap/horde.schema
</pre>
+</p>
-<p>Save the template and run <code>kolabconf</code> to update OpenLDAP to
-use the new schema file.</p>
+<p>Save the template and run <code>/kolab/sbin/kolabconf</code> to update
+OpenLDAP to use the new schema file.</p>
+</div>
-<h4>Step 8</h4>
+<hr />
-<p>Set up the Horde database in MySQL. This database is used to store general
-Horde information, as well as per-user settings such as category information, etc.
-You can also view these instructions in the <code>horde/scripts/db/README</code> file.</p>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step8"><h2>13. Step 8: Setup MySQL to accommodate the Horde datastore</h2></a>
-<p>You should first edit <code>/kolab/var/kolab/www/horde/scripts/db/mysql_create.sql</code>
-and change the Horde MySQL user password to something more secure. The section you need to
-edit looks like this:</p>
+<div class="section">
+<p>Set up the Horde database in MySQL. This database is used to store general
+Horde information, as well as per-user settings such as category information,
+etc. You can also view these instructions in the
+<code>horde/scripts/db/README</code> file.</p>
-<pre>
+<p>You should first edit
+<code>/kolab/var/kolab/www/horde/scripts/db/mysql_create.sql</code> and
+change the Horde MySQL user password to something more secure. The section
+you need to edit looks like this:
+<pre class="shell">
REPLACE INTO user (host, user, password)
VALUES (
'localhost',
'horde',
-- IMPORTANT: Change this password!
- PASSWORD('horde')
+ PASSWORD('<b>horde</b>')
);
</pre>
+</p>
-<p>Now add the Horde database:</p>
-
-<pre>
+<p>Now add the Horde database:
+<pre class="shell">
# mysql --user=root --password=<b>your-mysql-root-pw</b> < /kolab/var/kolab/www/horde/scripts/db/mysql_create.sql
# mysqladmin --user=root --password=<b>your-mysql-root-pw</b> reload
</pre>
+</p>
<p>To check that this is working, the following command should execute
-without errors:</p>
-
-<pre>
+without errors:
+<pre class="shell">
# mysql --user=horde --password=<b>your-horde-user-pw</b> horde
</pre>
+</p>
+</div>
-<h4>Step 9</h4>
+<hr />
+
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="step9"><h2>14. Step 9: Configure the Horde applications</h2></a>
+
+<div class="section">
<p>You now need to configure all the Horde applications. Log in to your Horde
-installation, at http://your.kolab.server/horde/.</p>
+installation, at <code>http://your.kolab.server/horde/</code>.</p>
-<ul>
-<li>Click on 'Administration', then 'Configuration'. You should see a list
-of available Horde applications.</li>
-<li>Go through this list and configure each Horde application as you please.
-You may want to choose 'Logout' in the 'Select any applications
-that should be linked in XXX's menu' section for each application's configuration,
-so that there is a 'Logout' menu option on the top menu for each application.
-The following configuration options should be adhered to for each application:</li>
-<li><b>!!! WARNING !!!</b><br /><br />
+<p>Click on <code>Administration</code>, then <code>Configuration</code>.
+You should see a list of available Horde applications.</p>
-Be sure to configure the 'Horde' module LAST, or else you will
-be locked out of the administration interface before everything has been properly configured -
-if this happens you'll have to re-checkout horde/config/conf.php.dist from Horde CVS
-and overwrite your auto-generated horde/config/conf.php with this .dist file. Also DO NOT
-click on 'Generate Configuration' when configuring Horde until you have gone through ALL
-the configuration tabs and entered the necessary variables as specified below. If you do click
-on this prematurely then you'll most probablly encounter fatal errors when trying to view
-any Horde pages, meaning you'll have to overwrite conf.php as above, and re-configure your
-Horde module.<br /><br />
+<p>Now go through this list and configure each Horde application as you
+please. You may want to choose <code>Logout</code> in the <code>Select any
+applications that should be linked in XXX's menu</code> section for each
+application's configuration, so that there is a <code>Logout</code> menu
+option on the top menu within each application.
+
+<div class="warning"><b>!!! WARNING !!!</b><br /><br />
+
+Be sure to configure the <code>Horde</code> module LAST, or else you will be
+locked out of the administration interface before everything has been
+properly configured - if this happens you'll have to re-checkout
+<code>horde/config/conf.php.dist</code> from Horde CVS and overwrite your
+auto-generated <code>horde/config/conf.php</code> with this .dist file. Also
+<b>DO NOT</b> click on <code>Generate Configuration</code> when configuring
+Horde until you have gone through <b>ALL</b> the configuration tabs and
+entered the necessary variables as specified below. If you do click on this
+prematurely then you'll most probably encounter fatal errors when trying to
+view any Horde pages, meaning you'll have to overwrite <code>conf.php</code>
+as above, and re-configure your <code>Horde</code> module.<br /><br />
<b>!!! WARNING !!!</b>
-</ul>
+</div>
+
+<p>The following configuration options should be adhered to for each
+application:</p>
<dl>
-<dt>Address Book (turba)</dt>
+<dt>Address Book (<code>turba</code>)</dt>
<dd>The default configuration should prove sufficient.</dd>
-<dt>Calendar (kronolith)</dt>
-<dd>Select the 'Kolab' driver for both the 'Calendar' and 'Free/Busy' sections.</dd>
+<dt>Calendar (<code>kronolith</code>)</dt>
+<dd>Select the <code>Kolab</code> driver for both the <code>Calendar</code>
+and <code>Free/Busy</code> sections.</dd>
-<dt>Filters (ingo)</dt>
+<dt>Filters (<code>ingo</code>)</dt>
<dd>The default configuration should prove sufficient.</dd>
-<dt>Mail (imp)</dt>
-<dd>Make sure the botton two options are checked on the 'Custom Hooks' tab.
-You may also want to specify the location of the ispell or aspell binary,
-if you have one of these installed, in the 'External Utilities and Menu'
-tab in order to allow users to spellcheck their email.</dd>
+<dt>Mail (<code>imp</code>)</dt>
+<dd>Make sure the botton two options are checked on the <code>Custom
+Hooks</code> tab. You may also want to specify the location of the
+<code>ispell</code> or <code>aspell</code> binary, if you have one of these
+installed, in the <code>External Utilities and Menu</code> tab in order to
+allow users to spellcheck their email.</dd>
-<dt>Notes (mnemo)</dt>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
+<dt>Notes (<code>mnemo</code>)</dt>
+<dd>Select the <code>Kolab</code> driver under the <code>Storage System</code>
+section.</dd>
-<dt>Password (passwd)</dt>
-<dd>Uncheck the option entitled 'Should we allow the user to specify the
-username?'.</dd>
+<dt>Password (<code>passwd</code>)</dt>
+<dd>Uncheck the option entitled <code>Should we allow the user to specify the
+username?</code>.</dd>
-<dt>Tasks (nag)</dt>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
+<dt>Tasks (<code>nag</code>)</dt>
+<dd>Select the <code>Kolab</code> driver under the <code>Storage System</code>
+section.</dd>
-<dt>Horde (horde)</dt>
-<dd><ul><li>Select the 'Kolab' tab and configure each entry to the values pertaining to
-your specific kolab server.</li>
-<li>Under the 'Database' tab, be sure to set the 'password'
-field to whatever you specified when creating the Horde database in MySQL.</li>
-<li>In the 'Authentication' tab, select <code>IMAP</code> as the authentication backend.
-Change the 'Configration type' to <code>Separate Values</code>, and set the 'Connection Protocol'
-to <code>imap/notls</code>. You may also want to specify a Kolab account in the
-'Administrators' field, for use in configuring Horde at a later stage. If you have a
-Kolab account such as <code>horde-admin at my.kolab.domain</code>, enter it here.</li>
-<li>(Optional) Under the 'Logging' tab, change the 'Path to the log file' to
-<code>/kolab/var/horde/horde.log</code>. For this to work you'll have to do the following:
-<pre>
+<dt>Horde (<code>horde</code>)</dt>
+<dd><ul><li>Select the <code>Kolab</code> tab and configure each entry to the
+values pertaining to your specific kolab server.</li>
+<li>Under the <code>Database</code> tab, be sure to set the
+<code>password</code> field to whatever you specified when creating the Horde
+database in MySQL.</li>
+<li>In the <code>Authentication</code> tab, select <code>IMAP</code> as the
+authentication backend. Change the <code>Configration type</code> to
+<code>Separate Values</code>, and set the <code>Connection Protocol</code>
+to <code>imap/notls</code>. You may also want to specify a Kolab account in
+the <code>Administrators</code> field, for use in configuring Horde at a later
+stage. If you have a Kolab account such as
+<code>horde-admin at my.kolab.domain</code>, enter it here.</li>
+<li>(Optional) Under the <code>Logging</code> tab, change the
+<code>Path to the log file</code> to <code>/kolab/var/horde/horde.log</code>.
+For this to work you'll have to do the following:
+<pre class="shell">
# mkdir -p /kolab/var/horde/
# chown kolab-n:kolab-n /kolab/var/horde/
</pre>
</li>
-<li>Under the 'Preference System' tab, select <code>LDAP</code> as the preferences driver, and enter the
-following values for each field (mirroring those specified under the 'Kolab' tab):<br />
-Base DN -> The same as Kolab\Base DN<br />
-DN of the root account -> The same as Kolab\Manager DN<br />
-Root DN password -> The same as Kolab\Manager Password<br />
-Username search key -> 'mail'
+<li>Under the <code>Preference System</code> tab, select <code>LDAP</code>
+as the preferences driver, and enter the following values for each field
+(mirroring those specified under the <code>Kolab</code> tab):<br />
+Base DN : The same as <code>Kolab -> Base DN</code><br />
+DN of the root account : The same as <code>Kolab -> Manager DN</code><br />
+Root DN password : The same as <code>Kolab -> Manager Password</code><br />
+Username search key : <code>mail</code>
</li>
-<li>Under the 'Mailer' tab, select <code>SMTP</code> as the mail send method.</li>
-<li>Under the 'Menu Settings' tab, check the 'Redirect to the Horde frameset after login' option.</li>
+<li>Under the <code>Mailer</code> tab, select <code>SMTP</code> as the mail
+send method.</li>
+<li>Under the <code>Menu Settings</code> tab, check the <code>Redirect to the
+Horde frameset after login</code> option.</li>
</ul>
</dd>
+</dl>
+</div>
+<hr />
-</dl>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="concl"><h2>15. Conclusion</h2></a>
-<h4>Conclusion</h4>
+<div class="section">
<p>*phew* That's it! You should now be able to log in to the webclient
-with any Kolab user. Quite a procedure to set it up, but I think you'll find it's worth it.
-We've put a lot of effort into the Webclient and as the current clients go,
-we'd like to think it's the best in terms of features :-) This guide is
-meant to tide users over until Horde releases their next stable version,
-at which time we can freeze the code and create an OpenPKG-compatible RPM
-that will greatly simplify this process of installing the webclient. Hang on
-till then!</p>
+with any Kolab user. Quite a procedure to set it up, but I think you'll find
+it's worth it. We've put a lot of effort into the Webclient and as the
+current clients go, we'd like to think it's the best in terms of features :-)
+This guide is meant to tide users over until Horde releases their next stable
+version, at which time we can freeze the code and create an OpenPKG-compatible
+RPM that will greatly simplify this process of installing the webclient. Hang
+on till then!</p>
+</div>
-<a name="opa"><h4>Appendix A</h4></a>
+<hr />
-<p>The OPA script; this should be put in your <code>~/.bashrc</code> or similar
-shell startup file.</p>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="opa"><h2>Appendix A: The <code>opa</code> script</h2></a>
-<pre>
+<div class="section">
+<p>The OPA script; this should be put in your <code>~/.bashrc</code> or similar
+shell startup file:
+<pre class="shell">
opa () {
root="$1"
if [ ! -d $root ]; then
@@ -508,17 +660,22 @@
eval `$root/etc/rc --eval all env`
}
</pre>
+</p>
+</div>
-<a name="obmconf"><h4>Appendix B</h4></a>
+<hr />
-<p>This <code>obmtool.conf</code> file can be used to install a Horde-ready Kolab installation
-based on OpenPKG 2.0.</p>
+<div class="toclnk"><a href="#toc">« ToC</a></div>
+<a name="obmconf"><h2>Appendix B: Horde-capable <code>obmtool.conf</code> file</h2></a>
-<pre>
+<div class="section">
+<p>This <code>obmtool.conf</code> file can be used to install a Horde-ready
+Kolab installation based on OpenPKG 2.0:
+<pre class="shell">
##
## obmtool.conf -- OpenPKG poor man's Boot, Build & Management Tool Configuration
## based on Ralf S. Engelschall's "obmtool.conf -- Development Tool Configuration"
-## Copyright (c) 2003 Thomas Lotterer <thomas at lotterer.net>
+## Copyright (c) 2003 Thomas Lotterer <thomas <b>at</b> lotterer <b>dot</b> net>
##
%common
@@ -628,5 +785,7 @@
echo "TAG = \"${TAG}\""
echo "TMPDIR=\"${TMPDIR}\""
</pre>
+</p>
+</div>
m4_include(footer.html.m4)
More information about the commits
mailing list