Calendar backend

The calendar backend is Everlock's CalDAV service.

It lets one Everlock instance host one or more calendar namespaces over HTTP, authenticate with normal Everlock users, and persist events as readable .ics files inside Everlock storage.

What it is for

Use the calendar backend when you want:

• personal or team calendars that stay inside the Everlock user model
• standard CalDAV clients such as Apple Calendar, Thunderbird, or mobile calendar apps to sync against Everlock
• auditable event storage in plain iCalendar files instead of a separate database-only format

How it fits in the system

The calendar backend owns:

• calendar collections and event resources
• CalDAV domain behavior
• authorization on http/calendar/<instance>
• persistence in one store per configured instance

The HTTP frontend owns discovery routing, authentication transport, and HTTP request handling.

Typical operator flow

1. enable the backend
2. create a calendar instance and assign a vhost
3. grant access to users or groups
4. connect a CalDAV client
5. create and sync events through the client

Pages

• CalDAV behavior and storage reference
• Users, groups, and access control
• Frontends

Read next

• Contacts backend
• Users, groups, and access control
• Architecture