[pkg-kolab] r323 - trunk/kolab-resource-handlers/debian

Noel Koethe noel at costa.debian.org
Mon Feb 20 08:42:43 UTC 2006


Author: noel
Date: 2006-02-20 08:42:42 +0000 (Mon, 20 Feb 2006)
New Revision: 323

Added:
   trunk/kolab-resource-handlers/debian/freebusy.conf
Modified:
   trunk/kolab-resource-handlers/debian/rules
Log:
provide own default freebusy.conf because the upstream is not complete

Added: trunk/kolab-resource-handlers/debian/freebusy.conf
===================================================================
--- trunk/kolab-resource-handlers/debian/freebusy.conf	2006-02-20 08:30:04 UTC (rev 322)
+++ trunk/kolab-resource-handlers/debian/freebusy.conf	2006-02-20 08:42:42 UTC (rev 323)
@@ -0,0 +1,75 @@
+<?php
+
+// What is the address of the Cyrus server where the calendar data is stored?
+$params['server'] = 'server.example.com';
+
+// 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=example,dc=com';
+
+// What DN should we use to bind to the LDAP server?
+$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';
+
+// 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']
+// we get the free/busy information from the script running on the other box
+$params['multi_location'] = true;
+
+// What LDAP attribute is used to store the users' home server address?
+$params['home_server'] = 'homeServer';
+
+// 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'] = 'example.com';
+
+// Are we using virtual domains with Cyrus?
+$params['virtual_domains'] = true;
+
+// Should we append domains to mailbox URIs? This only applies when
+// 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
+// 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';
+
+// What password should we use with the above account?
+$params['calendar_pass'] = 'fb';
+
+// What is the name of the users' calendar mailbox?
+$params['calendar_store'] = 'Calendar';
+
+// How many days of free/busy data should we generate?
+$params['freebusy_days'] = 56;
+
+// 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.
+$params['redirect'] = false;
+
+// Should we send a Content-Type header, indicating what the mime type of the
+// resulting VFB file is?
+$params['send_content_type'] = false;
+
+// Should we send a Content-Length header, indicating how large the resulting
+// VFB file is?
+$params['send_content_length'] = false;
+
+// Should we send a Content-Disposition header, indicating what the name of the
+// resulting VFB file should be?
+$params['send_content_disposition'] = false;
+
+// Where are we logging to?
+$params['log'] = 'file:/var/log/kolab/freebusy.log';                // File...
+// $params['log'] = 'syslog:cons, pid';            // Or syslog...
+
+// What level of output should we log? Higher levels give more verbose output.
+// One of: RM_LOG_SILENT; RM_LOG_ERROR; RM_LOG_WARN; RM_LOG_INFO or RM_LOG_DEBUG.
+$params['log_level'] = RM_LOG_DEBUG;
+

Modified: trunk/kolab-resource-handlers/debian/rules
===================================================================
--- trunk/kolab-resource-handlers/debian/rules	2006-02-20 08:30:04 UTC (rev 322)
+++ trunk/kolab-resource-handlers/debian/rules	2006-02-20 08:42:42 UTC (rev 323)
@@ -65,7 +65,7 @@
 
 	# Install conffiles
 	install -D -m 644 kolab-resource-handlers/resmgr/resmgr.conf debian/kolab-resource-handlers/etc/kolab/resmgr.conf
-	install -D -m 644 kolab-resource-handlers/freebusy/freebusy.conf debian/kolab-resource-handlers/etc/kolab/freebusy.conf
+	install -D -m 644 debian/freebusy.conf debian/kolab-resource-handlers/etc/kolab/freebusy.conf
 	install -D -m 644 debian/apache2-kolab.conf debian/kolab-resource-handlers/etc/kolab/apache2-kolab.conf
 	
 binary-arch: build install




More information about the pkg-kolab-devel mailing list