GutsyRecipe

Differences between revisions 31 and 32
Revision 31 as of 2008-01-12 23:43:27
Size: 7874
Editor: optussatellitebintb
Comment: Spellcheck
Revision 32 as of 2008-01-12 23:54:03
Size: 8050
Editor: optussatellitebintb
Comment: Added WebDAV howto
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
There are many ways of enabling other people to see your calendar, but the two most common, are what Evolution calls "On the web"-calendars (or webcal), and CalDAV-calendars. "On the web" calendars, are just that; they're calendar files stored on a web-server for clients to download. Nothing magical about it. Your calendar application will open a connection to the web-server, download the calendar file and use it just like a normal, local calendar, except in most cases it will be read-only. The application can also publish the calendar to the web-server using WebDAV. WebDAV, an abbreviation that stands for Web-based Distributed Authoring and Versioning, refers to the set of extensions to the Hypertext Transfer Protocol (HTTP) which allows users to collaboratively edit and manage files on remote World Wide Web servers. The "On the web"-type of calendar is suitable when you want anyone in the world to have access to the calendar. A TV-channel could use this to announce their program, for instance, or Free Software communities can use it to enable users to see how the project is progressing, release dates, etc. If this is all you want, then you don't really need a CalDAV server. Apache with mod_dav will do the trick. There are many ways of enabling other people to see your calendar, but the two most common, are what Evolution calls "On the web"-calendars (or webcal), and CalDAV-calendars. "On the web" calendars, are just that; they're calendar files stored on a web-server for clients to download. Nothing magical about it. Your calendar application will open a connection to the web-server, download the calendar file and use it just like a normal, local calendar, except in most cases it will be read-only. The application can also publish the calendar to the web-server using WebDAV.
Line 10: Line 10:
/!\ ''' It would be nice if someone would write a howto on that. ''' WebDAV, an abbreviation that stands for Web-based Distributed Authoring and Versioning, refers to the set of extensions to the Hypertext Transfer Protocol (HTTP) which allows users to collaboratively edit and manage files on remote World Wide Web servers. The "On the web"-type of calendar is suitable when you want anyone in the world to have access to the calendar. A TV-channel could use this to announce their program, for instance, or Free Software communities can use it to enable users to see how the project is progressing, release dates, etc. If this is all you want, then you don't really need a CalDAV server. Apache with mod_dav will do the trick. ([http://www.digital-arcanist.com/sanctum/article.php?story=20070427101250622 WebDAV with Apache 2.x on Ubuntu])
Line 51: Line 51:
Line 77: Line 76:
 * [http://www.digital-arcanist.com/sanctum/article.php?story=20070427101250622 HOWTO Enable WebDAV with Apache 2.x on Ubuntu Linux]

Warning /!\ THIS PAGE IS NOT FINISHED. DON'T FOLLOW ANY ADVICE IN IT UNTIL THIS LINE IS REMOVED.

This page explains how to install Apple's iCal Server (also called DCS or Darwin Calendar Server) on Ubuntu Server, though desktop variants should also work without any problems.

What is CalDAV?

There are many ways of enabling other people to see your calendar, but the two most common, are what Evolution calls "On the web"-calendars (or webcal), and CalDAV-calendars. "On the web" calendars, are just that; they're calendar files stored on a web-server for clients to download. Nothing magical about it. Your calendar application will open a connection to the web-server, download the calendar file and use it just like a normal, local calendar, except in most cases it will be read-only. The application can also publish the calendar to the web-server using WebDAV.

WebDAV, an abbreviation that stands for Web-based Distributed Authoring and Versioning, refers to the set of extensions to the Hypertext Transfer Protocol (HTTP) which allows users to collaboratively edit and manage files on remote World Wide Web servers. The "On the web"-type of calendar is suitable when you want anyone in the world to have access to the calendar. A TV-channel could use this to announce their program, for instance, or Free Software communities can use it to enable users to see how the project is progressing, release dates, etc. If this is all you want, then you don't really need a CalDAV server. Apache with mod_dav will do the trick. ([http://www.digital-arcanist.com/sanctum/article.php?story=20070427101250622 WebDAV with Apache 2.x on Ubuntu])

Built on top of WebDAV, CalDAV is a standard protocol, specified in [http://tools.ietf.org/html/rfc4791 RFC 4791], which enables advanced online calendar functions. Concepts such as users, groups, locations and resources are introduced, enabling collaborative scheduling. Different users of different groups can have different permissions to read and write to a calendar, etc. Also, a CalDAV calendar doesn't use a single file, but stores calendar events as files in directories. It also handles recurring events, enables free/busy lookups, etc. This makes CalDAV suitable for an office environment.

Install procedure for Ubuntu Server 7.10

Installing Apple's iCal Server is fairly trivial once you know what to do. You do need to download some additional packages using apt-get, and you'll need to download some software using subversion. Most users will be familiar with apt-get, many with subversion. If you're not familiar with subversion, don't panic. This guide will be a detailed, step by step howto, showing exactly which commands to enter and when.

To make this work you will need to enable the Universe repositories (see ["AddingRepositoriesHowto"] and remember to do an  apt-get update  afterwards).

Ready?

  • Log into the server console or via ssh, so you can enter commands, and run  sudo -s  to get a root shell.

  • Install some software:

     apt-get install subversion libkrb5-dev attr curl build-essential libssl-dev python-pysqlite2 bzip2 

  • Install some more software:

     apt-get install curl zope3 python-xml python-pyopenssl python-dateutil python-xattr python-pysqlite2 python-twisted python-vobject python-kerberos 

  • We now need to edit our /etc/fstab file and add  user_xattr  to the options for the partition containing the CalDAV server, / in this case:  vim /etc/fstab  This is what the /etc/fstab change looks like: {{{ Before: UUID=94a96528-c889-45a1-bc98-d9d02ecdd59c / ext3 defaults,errors=remount-ro 0 1

After : UUID=94a96528-c889-45a1-bc98-d9d02ecdd59c / ext3 defaults,errors=remount-ro,user_xattr 0 1 }}}

Warning /!\ You must modify the settings for the partition on which you're installing the server. So if your /opt is on a different partition, you must set the  user_xattr  flag and modify the instructions below.

  • Remount the file system (to activate user_xattr):  mount -o remount / 

  • We'll install the server in /opt, so lets change into it:  cd /opt 

  • Let's download the server software itself using subversion:

     svn checkout http://svn.macosforge.org/repository/calendarserver/CalendarServer/trunk CalendarServer 

  • Subversion has downloaded a lot of software, and created a directory for us, called CalendarServer. Let's change into it:  cd CalendarServer 

  • And run a script to download some necessary packages, configure, etc:  ./run -s 

  • Our CalDAV server is almost ready for action. Let's copy the test configuration so we can get it up as quickly as possible. Real configuration can wait:  cp conf/caldavd-test.plist conf/caldavd-dev.plist 

  • We do need to do a little configuration though:  vim conf/caldavd-dev.plist 

  • First change the hostname for the server. Locate the line  <!-- Network host name -->  and change  <string>localhost</string>  to  <string>your-real-hostname</string>  (That is, put the actual name of your server inside the string, it's used within URLs within the software.)

  • To make the server available to connections from other computers. Locate this line:  <!-- List of IP addresses to bind to [empty = all] -->  and replace  127.0.0.1  in  <string>127.0.0.1</string>  with either nothing or a specific, public ip address for your server.

Warning /!\ [https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/160190 Bug #160190]: As of 2007-11-05 there is a bug in Evolution that prevents us from using this set-up to authenticate to the caldavd server. The report has contributions which explain how to enable Evolution to connect. It's not included here, because it's important that you check out the bug yourself.

  • Run the server:  ./run 

That's it! The server is up and running, and you can connect to it with your CalDAV client using  caldav://ADDRESS:8008/calendars/users/admin/calendar  to test the server using username  admin  and password  admin 

To Do:

We're not really done yet. So, what's next? We're currently running the server as root. That's not necessary, so we shouldn't. What we should do, is create a user for our CalDAV server, set permissions for /opt/CalendarServer to that user and run as that user. We should also create scripts for /etc/init.d/ so we can manage it like we do with other services, and we should add a script to run it when we boot and properly shut it down when we shut down the system.

We also need to set up users and permissions for the server itself, so people can connect to the server and share their calendars, which is what we've been aiming for.

We should also document where the server-data is stored, so the information that users have entrusted to the server can be backed up.

Ideally we should package this application so the installation is installable with a single command.

References:

CalendarServer/GutsyRecipe (last edited 2011-05-23 21:08:50 by cpc11-cdif12-2-0-cust1)