It is possible to remove all of the content from a Lion Calendar server using Postgres. To aid you in doing so, Apple has built out a couple of commands to make the process easier. This will nuke everything from the server and so is not something that should be lightly done. To do so, first stop the Calendar service in the Server application. Then let’s back up the database: pg_dump -U _postgres caldav -c -f /db_backups/caldav.sql Then run dropdb to remove the database itself: dropdb -U _postgres caldav Once the database is gone, run the calendar_bootstrap_database script (I prefer doing so verbosely): calendarserver_bootstrap_database -v Now you should be able…
-
-
Disabling and Redirecting CalDAV (aka Lion and Apache2)
Lion Server moves a few things around. Not only in regards to a little window dressing in the GUI apps, but also under the hood. One such example is the /ical extension often used to direct users to iCal’s little section of the web portal in OS X Server, no longer around in Lion. One could just redirect requests for /ical to /webcal as was done previously. But what if you wanted to actually redirect the CalDAV traffic to look at a directory other than /calendars on the web server (e.g. maybe your site already uses /calendars). To do so, check out /etc/apache2/servermgr_web_apache2_config.plist. About half way down are the proxies…
-
Mac OS X Server: CalDav Log Fun
The selected logfile does not exist. Ran into an interesting little problem again, where the iCal Server doesn’t create its log directory when you enable it. Not sure why this happens, but the first thing to do when you see this error is verify that the /var/log/caldavd directory is present on the system. If not: mkdir /var/log/caldavd Then, restart the service and see if access.log and error.log are created in this folder. If not: touch /var/log/caldavd/access.log touch /var/log/caldavd/error.log And for good measure: chmod 640 access.log chmod 640 error.log How did I know where those logs go? serveradmin settings calendar:ErrorLogFile; serveradmin settings calendar:AccessLogFile It’s therefore possible to actually decide you’d rather…
-
Mac OS X Server 10.5: Parsing and Formatting for CalDAV
I originally posted this at http://www.318.com/TechJournal A key aspect of any groupware solution is the ability to share calendars. Leopard server brings the long-awaited ability to share calendars to the Mac OS X Server platform. Leopard uses CalDAV as the back end protocol for Calendar sharing. CalDAV is currently supported by Facebook, Novell Evolution, Zimbra, Drupal, Microsoft Exchange, Kerio and now Mac OS X Server. CalDAV looks at each event as an HTTP resource, giving users the ability to view events in a web browser. Each event is stored in the iCalendar format. A typical event in the iCalendar format: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Apple Calendar//Calendar1//Charles Edge BEGIN:VTODO DTSTAMP:19980130T134500Z SEQUENCE:2 UID:uid4@host1.com ORGANIZER:MAILTO:riaa@us.gov…