stuart: doc/www/src webclient.html.m4,1.4,1.5
cvs at intevation.de
cvs at intevation.de
Thu Jan 27 16:53:11 CET 2005
Author: stuart
Update of /kolabrepository/doc/www/src
In directory doto:/tmp/cvs-serv18596
Modified Files:
webclient.html.m4
Log Message:
Better reflect the current status of the webclient installation procedure
Index: webclient.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/webclient.html.m4,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- webclient.html.m4 3 Oct 2004 13:04:41 -0000 1.4
+++ webclient.html.m4 27 Jan 2005 15:53:09 -0000 1.5
@@ -8,19 +8,25 @@
<hr />
<div class="warning">
-<b>NOTE: The Kolab Webclient has been re-designed to work exclusively with
+<b>NOTE: The webclient is considered EXPERIMENTAL and as such should NOT be
+used in production.</b> However, if you're feeling brave and want to help out
+with testing & identifying problems with the webclient, your help would be
+greatly appreciated. You may discuss any issues that you have on the
+<a href="/mailman/listinfo/kolab-devel">kolab-devel</a> mailing list. All bugs
+should be reported on the <a href="http://bugs.horde.org/">Horde bug
+tracker</a>.
+</div>
+
+<div class="warning">
+NOTE: The Kolab Webclient has been re-designed to work exclusively with
version 2 of the Kolab server. As this new version of Kolab is currently in
development it is recommended that you wait until it is fully released before
-running the webclient.</b>
+running the webclient. However, If you know how to get the latest Kolab 2
+snapshots up and running and want to help test the webclient, then this guide
+is for you.
</div>
<div class="section">
-<p>If you know how to get the latest Kolab 2 snapshots up and running and want
-to help test the webclient, then this guide is for you. Discussion around the
-webclient will be held on the
-<a href="http://example.com/mailman/listinfo/kolab-devel">kolab-devel</a>
-mailing list, so you are urged to subscribe if you're not already.</p>
-
<p>Credits and thanks must also go out to the
<a href="http://www.horde.org/">Horde project</a>, on which the Kolab Webclient
is based. The Kolab Webclient is essentially a composition of several Horde
@@ -28,6 +34,14 @@
with additional code allowing these applications to use a Kolab server as a
groupware backend.</p>
+<p>You may also find additional information about the webclient installation
+on the <a href="http://wiki.kolab.org/">Kolab Wiki</a> - if you encounter
+problems when installing the webclient be sure to visit the wiki. It is updated
+more frequently than this guide and as such will probably contain additional
+information to help you out. Specifically, be sure to take a look at the
+<a href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde">Kolab2 Installation - Horde</a>
+page.</p>
+
<p>Before you begin with this guide, it is recommended that you put the
following in the <code>~/.cvsrc</code> file of the user who will be checking
out and installing the webclient code from CVS (usually <code>root</code>):
@@ -63,6 +77,7 @@
<li><a href="#optional">Optional</a>
<ol>
<li><a href="#opt_phpa">PHP Accelerator</a></li>
+<li><a href="#opt_opa">OPA Script</a></li>
</ol>
</li>
@@ -80,23 +95,26 @@
<p>Horde requires a SQL server to store various server and user data. Several
SQL servers are supported, however only two are covered here (as they are part
of OpenPKG and as such are easy to install alongside Kolab):
-<a href="ftp://ftp.openpkg.org/release/2.1/SRC/mysql-4.0.20-2.1.0.src.rpm">MySQL</a>
+<a href="ftp://ftp.openpkg.org/release/2.2/UPD/mysql-4.0.21-2.2.1.src.rpm">MySQL</a>
and
-<a href="ftp://ftp.openpkg.org/release/2.1/SRC/postgresql-7.4.3-2.1.0.src.rpm">PostgreSQL</a>.
+<a href="ftp://ftp.openpkg.org/release/2.2/UPD/postgresql-7.4.5-2.2.1.src.rpm">PostgreSQL</a>.
</p>
<p>Select the SQL server that you wish to use above and install the necessary
-RPM. With either selection, you will need to recompile your Apache RPM with
-additional flags in order to allow mod_php to support your chosen SQL variant.
+RPM. With either selection, you will need to recompile your Apache and PHP RPMs
+with additional flags in order to allow PHP to support your chosen SQL variant.
For MySQL you'll need:
<pre class="shell">
---with=mod_php_mysql
+--with=mod_php_mysql # for your apache rpm
+--with=mysql # for your php rpm
</pre>
and for PostgreSQL you'll need:
<pre class="shell">
---with=mod_php_pgsql
+--with=mod_php_pgsql # for your apache rpm
+--with=pgsql # for your php rpm
</pre>
-in addition to Apache's existing <code>--with</code> flags, of course.</p>
+in addition to the existing <code>--with</code> flags for both packages,
+of course.</p>
<p>For those of you who are interested: the dependency on a SQL server can be
dropped if a LDAP driver is written for the Horde Datatree system, in which case
@@ -114,8 +132,16 @@
<pre class="shell">
# /kolab/bin/pear install -f Net_IMAP Log Mail_Mime File Date
-</pre>
-</p>
+</pre></p>
+
+<p>If you receive errors about being unable to modify files and directories
+because of safe_mode being in effect, then you'll have to modify your
+<code>/kolab/etc/php/php.ini</code> file and disable safe mode. The line in
+question should look like the following after modification:
+
+<pre class="shell">
+safe_mode = off ; Enable Safe Mode (file UID comparisons)
+</pre></p>
</div>
<div class="toclnk"><a href="#toc">↑ contents</a></div>
@@ -144,7 +170,7 @@
# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository checkout framework imp kronolith mnemo nag passwd turba ingo
</pre>
You now need to install the Horde Framework (this must be run within the Kolab
-OpenPKG environment, e.g. by using the <code>opa</code> script):
+OpenPKG environment, e.g. by using the <a href="#opt_opa">opa</a> script):
<pre class="shell">
# cd framework
# /kolab/bin/php install-packages.php
@@ -254,13 +280,14 @@
<p>You now need to configure all the Horde applications. Log in to your Horde
installation, at <code>http://your.kolab.server/horde/</code>. Once you're in,
click on the <code>Administration</code> link on the sidebar, then the
-<code>Configuration</code> sub-option.You should see a list of available Horde
+<code>Setup</code> sub-option. You should see a list of available Horde
applications in the main frame - you now need to go through this list and
configure each Horde application as you please. Click on an entry in this list;
-you should be brought to a configuration screen. Go through each page within
-this screen and change any settings as you see fit (although the default options
+you should be brought to a configuration screen. Go through each tab within
+this screen (if there are multiple tabs; otherwise there will just be a single
+page) and change any settings as you see fit (although the default options
are usually sufficient if you don't feel comfortable editing all the available
-variables); once you have finished configuring an application, click on the
+variables). Once you have finished configuring an application, click on the
<code>Generate XXX Configuration</code> button at the bottom of the page to
auto-generate the relevant <code>conf.php</code> file for the specific
application. Repeat this process for every application in the
@@ -296,6 +323,9 @@
<li>In the <code>Preference System</code> tab, select <code>Kolab (LDAP)</code>
as the preferences driver (again, should be the last entry in the drop-down
list).</li>
+<li>In the <code>DataTree System</code> tab, select <code>SQL Database</code>
+as the DataTree backend storage. Make sure the <code>Driver configuration</code>
+is also set to <code>Horde defaults</code>.</li>
<li>In the <code>Mailer</code> tab, select <code>Use a SMTP server</code> as
the method for sending mail.</li>
<li>In the <code>Virtual File Storage</code>, leave the VFS backend selection
@@ -305,14 +335,14 @@
<li>Finally, in the <code>Kolab Groupware Server</code> tab, change the
<code>Horde/Kolab integration status</code> field to <code>enabled</code> and
set each field in the resulting screen to the values pertaining to your
-specific kolab installation. The most important of these correspond the those
+specific kolab installation. The most important of these correspond to those
in your <code>/kolab/etc/kolab/kolab.conf</code> file.</li>
</ul>
</dd>
<dt>Mail (<code>imp</code>)</dt>
-<dd>Make sure the bottom two options are checked on the <code>Custom
-Hooks</code> tab. You may also want to specify the location of the
+<dd><!-- Make sure the bottom two options are checked on the <code>Custom
+Hooks</code> tab. --> You may 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. There is also the option of using a
@@ -402,6 +432,43 @@
by Nick Lindridge
</pre>
</p>
+</div>
+
+<div class="toclnk"><a href="#toc">↑ contents</a></div>
+<a name="opt_opa"><h3>3.2. OPA Script</h3></a>
+
+<div class="section">
+<p>The OPA script is a small shell script used to place the current session in
+the Kolab (or indeed any OpenPKG) environment. This is generally needed when
+working with the Kolab server; otherwise you run the risk of your base systems'
+utilities handling commands instead of the corresponding Kolab programs.</p>
+
+<p>To place yourself in the Kolab environment using the OPA script, you simply
+type the following (assuming your kolab hierarchy is stored in the
+<code>/kolab</code> directory):
+<pre class="shell">
+# opa /kolab
+</pre>
+</p>
+
+<p>Place this script in your <code>~/.bashrc</code> file, or other similar such
+shell startup file.
+<pre class="shell">
+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>
+</p>
+
</div>
m4_include(footer.html.m4)
More information about the commits
mailing list