CalendarServer
|
Size: 8568
Comment:
|
Size: 4738
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from CalDAVServer /!\ ''' THIS PAGE IS NOT FINISHED. CONSIDER THE INSTRUCTIONS OF ALPHA RELEASE QUALITY. ''' ''If you have any problems with any of the instructions here, please provide comment and feedback.'' |
This page explains how to install Apple's [[http://en.wikipedia.org/wiki/Darwin_Calendar_Server|Darwin Calendar Server]] (also called DCS, and the basis for their iCal Server). |
| Line 5: | Line 3: |
| In Intrepid Ibex, Apple's calendar server was installable as the calendarserver package. Unfortunately, this no longer works (as of 7 Feb 2010) with Ubuntu Jaunty (9.04) or Karmic (9.10) servers, necessitating these recipes for installation steps. The problem seems to result from required corrections to the upstream Debian package, which is not being actively maintained now. There is a [[https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/403349|bug #403349]] filed about this. Please see the bug and the link below for work on packaging for Ubuntu Karmic (9.10) server. | |
| Line 6: | Line 5: |
| This page explains how to install Apple's [[http://en.wikipedia.org/wiki/Darwin_Calendar_Server|Darwin Calendar Server]] (also called DCS, and the basis for their iCal Server) on Ubuntu Gutsy. | There are many other Calendar Servers, so the title of this page is misleading. There are also other CalDAV serves, including DAViCal, some of which work better than the Darwin Calendar Server. The reader is advised to research other calendar servers and keep in mind the limited scope of these instructions. |
| Line 15: | Line 14: |
| == Recipes for Installation == | |
| Line 16: | Line 16: |
| == 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. |
[[CalendarServer/GutsyRecipe|Gutsy]] [[CalendarServer/KarmicRecipe|Karmic]] |
| Line 19: | Line 19: |
| To make this work you will need to enable the Universe repositories (see [[AddingRepositoriesHowto]] and remember to do an {{{ apt-get update }}} afterwards). | == Configuration == |
| Line 21: | Line 21: |
| Ready? | There is now a [[CalendarServer/Configuration|page]] regarding configuration of the caldavd server. |
| Line 23: | Line 23: |
| * 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 }}} |
== Packaging == |
| Line 30: | Line 25: |
| 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 }}} /!\ 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. This is because Calendar Server uses extended filesystem attributes to store WebDAV properties. * Remount the file system (to activate user_xattr): {{{ mount -o remount / }}} * Create a directory for our server to live in; {{{ mkdir /opt/caldavd }}} * and change into it, {{{ cd /opt/caldavd }}} * 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. /!\ [[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. * Create a user and group to give our server an identity of its own, but we don't need a home directory for it; {{{ adduser --system --group caldavd --no-create-home }}} * Set permissions; {{{ chown -R caldavd:caldavd /opt/caldavd }}} * Run the server: {{{ sudo -u caldavd -b /opt/caldavd/CalendarServer/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 should 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. |
Of course, the best solution is for a newer version of calendar server to be appropriately packaged, so that people can readily install it. There is now a [[CalendarServer/Packaging|wiki page]] about progress on this. |
This page explains how to install Apple's Darwin Calendar Server (also called DCS, and the basis for their iCal Server).
In Intrepid Ibex, Apple's calendar server was installable as the calendarserver package. Unfortunately, this no longer works (as of 7 Feb 2010) with Ubuntu Jaunty (9.04) or Karmic (9.10) servers, necessitating these recipes for installation steps. The problem seems to result from required corrections to the upstream Debian package, which is not being actively maintained now. There is a bug #403349 filed about this. Please see the bug and the link below for work on packaging for Ubuntu Karmic (9.10) server.
There are many other Calendar Servers, so the title of this page is misleading. There are also other CalDAV serves, including DAViCal, some of which work better than the Darwin Calendar Server. The reader is advised to research other calendar servers and keep in mind the limited scope of these instructions.
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 simply iCalendar files stored on a web-server for clients to download. Nothing magical about it. Your calendar application will open a normal http 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 will do the trick, with with mod_dav if you want WebDAV publishing support. (WebDAV with Apache 2.x on Ubuntu)
Built on top of WebDAV, CalDAV is a standard protocol, specified in 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.
Recipes for Installation
Configuration
There is now a page regarding configuration of the caldavd server.
Packaging
Of course, the best solution is for a newer version of calendar server to be appropriately packaged, so that people can readily install it. There is now a wiki page about progress on this.
References:
CalendarServer (last edited 2014-07-13 21:21:52 by 5ac9a5f8)