Setup DAViCal under Debian 7.1 “Wheezy”

apt-get install davical

do all the things needed to get Apache SSL working, including:

zless /usr/share/doc/apache2.2-common/README.Debian.gz
start here by reading this, “SSL” section.

make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/ssl/private/jyoti.alaya.net.crt

vim /etc/apache2/sites-available/default-ssl
SSLCertificateFile /etc/ssl/private/jyoti.alaya.net.crt
#SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

a2ensite default-ssl
a2enmod ssl

test https://your.site.com see if it works

see http://davical.org/installation.php Database Setup section. Setup db users and create PostgreSQL database following instructions. Database creation command is:
su postgres -c /usr/share/davical/dba/create-database.sh

Remember to restart the database.

In Apache Configuration section, if using SSL (recommended) then I would *not* use a virtual host. Instead I would choose the more simple method mentioned as “Relative to an existing DocumentRoot”. This way the SSL will not be only for this one particular VirtualHost but could be used for other purposes on server.

see http://wiki.davical.org/w/Debian and see info for “edit /etc/php5/apache2/php.ini”

cp /usr/share/doc/davical/examples/davical-conf.php/example-config.php.gz /etc/davical/config.php.gz
gunzip /etc/davical/config.php.gz


get admin password from database (is the string of characters after the **)
su - postgres -c "psql davical -c 'select username, password from usr;'"

browse to https://your.server.com/davical/ and login as admin

To create user go to “User Functions” -> “Create Principal”

Add username, password, full name, etc. For perms click Read/Write and make sure all boxes checked except “Override a Lock”, “Read Access Controls”, and “Write Access Controls”

For a more restricted user uncheck appropriate boxes accordingly.

To migrate an existing (such as Google) calendar into a new one created:
export the existing calendar in the client as .ics format

In DAViCal admin panel select “User Functions” -> “List Users” -> click on ID of user to import calendar into.

Under “Principal Collections” click on ID of user’s calendar.
In “Load From File:” select the .ics file you just exported and click “Apply Changes” below.

This method is better for migrating existing calendars than doing it in the client because it is more efficient for the server and avoids latency problems and possible issues creating a large number of entries in the database through the client’s https connection.

If you try importing the .ics into the fresh calendar on the client some of the database writes may fail (You may see something like this in /var/log/apache2/error.log: davical: LOG: PUT: Query: Possible slow query: SQ in ‘/usr/share/davical/inc/caldav PUT-functions.php’ on line 1379) because of the overwhelming amount of db transactions flooding the server.

Finally, to set up the client choose option to create new network calendar and use https://your.server.com/davical/caldav.php/user/calendar as the address.