Contacts backend

The contacts backend is Everlock's CardDAV service.

It provides hosted address books over HTTP, backed by Everlock storage and the same user and grant model used everywhere else in the system.

What it is for

Use the contacts backend when you want:

• one or more shared or private address books behind Everlock auth
• standard CardDAV clients to sync against Everlock
• human-readable .vcf contact storage instead of opaque database rows

How it fits in the system

The contacts backend owns:

• address-book and contact resources
• CardDAV-specific behavior
• authorization on http/contacts/<instance>
• persistence in a dedicated store per instance

The HTTP frontend owns HTTP auth flow, host routing, and wire transport.

Typical operator flow

1. enable the backend
2. create a contacts instance and assign a vhost
3. grant user or group access
4. connect a CardDAV client
5. sync contact changes through the client

Pages

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

Read next

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