gunnar: server/kolab-resource-handlers/kolab-resource-handlers/freebusy freebusy.conf, 1.4, 1.5
cvs at kolab.org
cvs at kolab.org
Fri Aug 3 12:32:45 CEST 2007
Author: gunnar
Update of /kolabrepository/server/kolab-resource-handlers/kolab-resource-handlers/freebusy
In directory doto:/tmp/cvs-serv13030
Modified Files:
freebusy.conf
Log Message:
Sync the conf file with the template in kolabd.
Index: freebusy.conf
===================================================================
RCS file: /kolabrepository/server/kolab-resource-handlers/kolab-resource-handlers/freebusy/freebusy.conf,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- freebusy.conf 2 Mar 2007 04:39:40 -0000 1.4
+++ freebusy.conf 3 Aug 2007 10:32:43 -0000 1.5
@@ -1,17 +1,23 @@
<?php
+// Kolab prefix
+$params['kolab_prefix'] = '/kolab';
+
// What is the address of the Cyrus server where the calendar data is stored?
// This is also used as the LDAP server address where user objects reside
$params['server'] = 'localhost';
+// What is the address of the LDAP server address where user objects reside
+$params['ldap_uri'] = "ldap://127.0.0.1:389";
+
// What is the Base DN of our LDAP database?
-$params['base_dn'] = 'dc=oberon';
+$params['base_dn'] = 'dc=example,dc=com';
// What DN should we use to bind to the LDAP server?
-$params['bind_dn'] = 'cn=manager,' . $params['base_dn'];
+$params['bind_dn'] = 'cn=nobody,cn=internal,' . $params['base_dn'];
// What password should we use with the above DN when binding?
-$params['bind_pw'] = 'password';
+$params['bind_pw'] = 'php password from kolab.conf';
// Are we using a multi-location setup? If this is true, we check the users'
// LDAP object for the next attribute - if it is different than $params['server']
@@ -19,11 +25,11 @@
$params['multi_location'] = true;
// What LDAP attribute is used to store the users' home server address?
-$params['home_server'] = 'homeServer';
+$params['home_server'] = 'kolabhomeserver';
// What is our default mail domain? This is used if any users do not have
// '@domain' specified after their username as part of their email address.
-$params['email_domain'] = 'oberon.co.za';
+$params['email_domain'] = 'example.com';
// Are we using virtual domains with Cyrus?
$params['virtual_domains'] = true;
@@ -32,13 +38,14 @@
// virtual_domains is true, and when using manager accounts.
$params['append_domains'] = false;
-// What account should we use to read in calendar data? This account should
+// What account should we use to read in calendar data in the case the user
+// does not supply credentials? This account should
// have access to the calendar mailbox of all the users for which free/busy
// information is to be retrieved.
-$params['calendar_user'] = 'fb at oberon.co.za';
+//$params['calendar_user'] = '@ @@cyrus-admins@@@';
// What password should we use with the above account?
-$params['calendar_pass'] = 'fb';
+//$params['calendar_pass'] = '@ @@bind_pw@@@';
// What is the name of the users' calendar mailbox?
$params['calendar_store'] = 'Calendar';
@@ -46,6 +53,14 @@
// How many days of free/busy data should we generate?
$params['freebusy_days'] = 56;
+// Should we generate extended free/busy information? This can be overridden by
+// the URL parameter "x" (= 0 or 1).
+$params['extended'] = false;
+
+// Should we use the caching mechanism, which avoids having to always re-read
+// all the events? This can be overridden by the URL parameter "c" (= 0 or 1).
+$params['cache'] = true;
+
// Should we redirect using a Location header, if the user is not local? If this
// is false we silently download the file ourselves and output it so that it
// looks as though the free/busy information is coming from us.
@@ -63,23 +78,43 @@
// resulting VFB file should be?
$params['send_content_disposition'] = false;
-// What db type to use for freebusy caches
-$params['dbtype'] = 'db4';
+// Where are we logging to?
+$params['log'] = 'file:file:/kolab/var/resmgr/freebusy.log'; // File...
+// $params['log'] = 'syslog:cons, pid'; // Or syslog...
-// Logging
-$params['log'] = "syslog:";
-$params['log_level'] = 2;
+// What level of output should we log? Higher levels give more verbose output.
+// One of: 0 (RM_LOG_SILENT); 1 (RM_LOG_ERROR); 2 (RM_LOG_WARN); 3 (RM_LOG_INFO) or 4 (RM_LOG_DEBUG).
+$params['log_level'] = 4;
+
+// What db type to use for freebusy caches
+$params['dbtype'] = 'db4';
// IMAP options passed to imap_open
-$params['imap_options'] = "/notls/secure/readonly";
+//$params['imap_options'] = "/notls/secure/readonly";
+$params['imap_options'] = "/notls/readonly";
-// Directory prefixes
-$params['kolab_prefix'] = "";
-$params['cache_dir'] = "/datastore/freebusy"; // default: /var/kolab/www/freebusy/cache
+$params['pfb_dbformat'] = 'db4';
-$params['pfb_dbformat'] = "db4";
+// Location of the cache files
+$params['cache_dir'] = '/kolab/var/kolab/www/freebusy/cache';
// don't change this if you don't have to
-+$params['ldap_uri'] = "";
-+$params['ldap_classname_suffix'] = "_dummy";
+//$params['ldap_classname_suffix'] = "_dummy";
+// Activate if you wish to use the new horde framework
+// (horde-framework-kolab) package instead of the old code in
+// kolab-horde-framework. This is still untested and considered
+// UNSAFE!
+$params['use_new_horde'] = false;
+
+//!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+//
+// If you modify this file, please do not forget to modify both the
+// template and the source file in kolab-resource-handler.
+//
+// In order to check if both are in sync:
+//
+// cd server
+// diff -Nau kolab-resource-handlers/kolab-resource-handlers/freebusy/freebusy.conf kolabd/kolabd/templates/freebusy.conf.template.in
+//
+//!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
More information about the commits
mailing list