[Kolab-devel] gunnar: server/patches/horde/turba-3.2-rc2 HK-GW-Config_turba-3.2-rc2.patch, NONE, 1.1 HK-GW-Fix_editing_contacts_turba-3.2-rc2.patch, NONE, 1.1 HK-GW-Fix_share_id_change_turba-3.2-rc2.patch, NONE, 1.1 HK-GW-Ldap_read_only_fix_turba-3.2-rc2.patch, NONE, 1.1

[Richard Bos]

Op Thursday 21 February 2008 08:38:57 schreef Gunnar Wrobel:
> > I have a question about the patches.  I see that the recent horde patches
> > include the settings (config.php), this in contradiction to the previous
> > patches.  How does this effect the horde installation on non openpkg
> > installations?  I mean we used to configure Horde via it's portal,
> > following this procedure:
> > http://en.opensuse.org/Kolab#Configuring_horde
>
> the configuration of Horde on Kolab2/OpenPKG and Kolab2/Gentoo always
> happened automatically. I consider this easier for the user since the
> Horde configuration is not trivial. Especially if you configure it for
> Kolab a user unfamiliar with the system may easily misconfigure it.

;)

> So far I had the "conf.php" files alongside with the *.spec files (see
> server/horde). I am going to change that with the new patch set but
> you are free to decide if you want to use them or not.

Ah, I see now.  The diffs actually add the config.php.  So, they can indeed by 
either left in or out, as desired by the packages.  The biggest challenge 
will probably be, how to stay in sync with the changes in horde....

> > Is this not necessary anymore.  How about system dependend settings, like
> > the imap server, uid, user password and the like?
>
> There are only two applications ("horde" and "kronolith" that require
> system specific variables). Check their ocnfiguration to see how that
> works. The additional "kolab.php" is not optimal but on Kolab2/OpenPKG
> we will deny the users access to the administration part of Horde
> anyhow. 

How, are the kolab configuration variables populated?  With a template 
mechanism, or differently?

diff -r 9884c84c8c49 horde/config/kolab.php
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/horde/config/kolab.php    Wed Feb 20 17:24:48 2008 +0100
@@ -0,0 +1,12 @@
+<?php
+$conf['log']['name'] = '@@@webserver_logdir@@@/horde/horde.log';
+$conf['cookie']['domain'] = '@@@fqdnhostname@@@';
+$conf['problems']['email'] = 'postmaster@@@@postfix-mydomain@@@';
+$conf['problems']['maildomain'] = '@@@postfix-mydomain@@@';
+$conf['kolab']['ldap']['server'] = '@@@fqdnhostname@@@';

This looks more or less like a kolab template to me....

> They can of course activate admin access but once they do that 
> one can assume they Horde already a little bit better.
>
> Btw. the patches are not well tested yet. I still need to fix
> kronolith and only then I'll move to real machines and do some real
> world testing.



-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.