CalendarServer
|
Size: 3866
Comment:
|
← Revision 76 as of 2014-07-13 21:21:52 ⇥
Size: 3401
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. DON'T FOLLOW ANY ADVISE IN IT UNTIL THIS LINE IS REMOVED. |
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 4: | Line 3: |
This page will explain how to install Apple's iCal Server on Ubuntu Server, though desktop variants should also work without any problems. |
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 8: | Line 6: |
| Explain that here, together with an explanation between CalDAV and WebDAV/webcal, with a link to a page describing how to make that happen. | 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 [[http://en.wikipedia.org/wiki/Webcal|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. |
| Line 10: | Line 8: |
| == Install procedure for Ubuntu Server 7.10 == | 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. ([[http://www.digital-arcanist.com/sanctum/article.php?story=20070427101250622|WebDAV with Apache 2.x on Ubuntu]]) |
| Line 12: | Line 10: |
| Installing Apple's iCal Server is fairly trivial once you know what to do. We do need to download some additional packages using apt-get, and we 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. | 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. |
| Line 14: | Line 12: |
| Ready? | == Configuration == |
| Line 16: | Line 14: |
| * 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 }}} |
There is a [[CalendarServer/Configuration|page]] regarding configuration of the caldavd server. |
| Line 20: | Line 16: |
| * 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 how my change looked 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 }}} * We must now remount the filesystem: {{{ 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 alot of software, and created a directory for us, called CalendarServer. Let's change into it: {{{ cd CalendarServer }}}[[BR]] * And run a script to download some necessary packages, configure, etc: {{{ ./run -s }}} * Ok, 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 some configuration though: {{{ vim conf/caldavd-dev.plist }}} * Let's change the hostname for the server. Locate the line {{{ <!-- Network host name --> }}} and change {{{ <string>localhost</string> }}} to {{{ <string>your-real-hostname</string> }}} [[BR]] * We have to make it 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 spesific, public ip address for your server. * There is a bug in Evolution that prevents us from using this setup. The bug is located here, and please visit it now to see if it's been fixed. It also explains how to enable Evolution to connect. I won't include it here, because it's important that you check out the bug yourself: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/16019 * Run the server: ./run * That's it! :) References: Cam's blog: [[BR]] http://cam.moobox.org/blog/?p=5 [[BR]] [[BR]] Lenfis blog: [[BR]] http://blog.jl42.de/index.php?/archives/231-Installation-of-the-Apple-Calendar-Server-on-Ubuntu-Edgy.html [[BR]] [[BR]] Calendar Server wiki: [[BR]] http://trac.macosforge.org/projects/calendarserver/wiki/ [[BR]] [[BR]] |
== References: == * [[http://tools.ietf.org/html/rfc4791|CalDAV protocol specification, RFC 4791]] * [[http://cam.moobox.org/blog/?p=5|Cam's blog]] * [[http://www.recycledpapyr.us/2008/01/09/installing-apples-darwin-calendar-server/|JT's blog]] * [[http://trac.macosforge.org/projects/calendarserver/wiki/|Calendar Server wiki]] * [[http://www.nabble.com/Re:-'Run'-script-crashes-p11433982.html|Maxime Wacker's trouble shooting tips]] * [[http://en.wikipedia.org/wiki/Caldav|CalDAV - Wikipedia entry]] * [[http://en.wikipedia.org/wiki/WebDAV|WebDAV - Wikipedia entry]] * [[http://www.digital-arcanist.com/sanctum/article.php?story=20070427101250622|HOWTO Enable WebDAV with Apache 2.x on Ubuntu Linux]] |
This page explains how to install Apple's Darwin Calendar Server (also called DCS, and the basis for their iCal 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.
Configuration
There is a page regarding configuration of the caldavd server.
References:
CalendarServer (last edited 2014-07-13 21:21:52 by 5ac9a5f8)