stuart: doc/www/src cvs-kolab.html.m4,1.4,1.5

cvs at intevation.de cvs at intevation.de
Thu Apr 29 12:22:17 CEST 2004


Author: stuart

Update of /kolabrepository/doc/www/src
In directory doto:/tmp/cvs-serv18491

Modified Files:
	cvs-kolab.html.m4 
Log Message:
Fixed up some incorrect HTML entities
Fixed up the incorrect definition lists
Added a new mandatory configuration step for the 'Horde' module
Added a warning about incorrect configuration of the 'Horde' module


Index: cvs-kolab.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/cvs-kolab.html.m4,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- cvs-kolab.html.m4	26 Apr 2004 15:22:37 -0000	1.4
+++ cvs-kolab.html.m4	29 Apr 2004 10:22:15 -0000	1.5
@@ -86,7 +86,7 @@
 or to the <a href="http://www.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.
+<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>
@@ -313,32 +313,32 @@
 you need to edit, and what needs to be done in each file, is as follows:</p>
 
 <dl>
-<di><code>horde/config/registry.php</code></di>
-<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>.
+<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>
 
-<di><code>imp/config/servers.php</code></di>
+<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>
 
-<di><code>ingo/config/backends.php</code></di>
+<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>
 
-<di><code>passwd/config/backends.php</code></di>
+<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>
 
-<di><code>turba/config/sources.php</code></di>
+<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>
@@ -417,26 +417,55 @@
 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>
-<di>Address Book (turba)</di>
+<dt>Address Book (turba)</dt>
 <dd>The default configuration should prove sufficient.</dd>
 
-<di>Calendar (kronolith)</di>
+<dt>Calendar (kronolith)</dt>
 <dd>Select the 'Kolab' driver for both the 'Calendar' and 'Free/Busy' sections.</dd>
 
-<di>Filters (ingo)</di>
+<dt>Filters (ingo)</dt>
 <dd>The default configuration should prove sufficient.</dd>
 
-<di>Horde (horde)</di>
+<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 'IMAP' as the authentication backend.
-Change the 'Configration type' to 'Separate Values', and set the 'Connection Protocol'
-to 'imap/notls/novalidate-cert'. You may also want to specify a Kolab account in the
+<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
@@ -446,32 +475,19 @@
 # chown kolab-n:kolab-n /kolab/var/horde/
 </pre>
 </li>
-<li>Under the 'Preference System' tab, select 'LDAP' as the preferences driver, and enter the
+<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'
+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 SMTP as the mail send method.</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>
 
-<di>Mail (imp)</di>
-<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>
-
-<di>Notes (mnemo)</di>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
-
-<di>Password (passwd)</di>
-<dd>Uncheck the option entitled 'Should we allow the user to specify the
-username?'.</dd>
 
-<di>Tasks (nag)</di>
-<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
 </dl>
 
 <h4>Conclusion</h4>





More information about the commits mailing list