Files backend

The files backend is Everlock's WebDAV service.

It serves one or more file shares over HTTP, authenticates with normal Everlock users, and keeps every file — and every version of every file — in Everlock storage. A share mounts as a drive in Finder, in the Linux file managers, and in Windows Explorer over HTTPS, and works with rclone, Cyberduck, and the mobile DAV apps.

What it is for

Use the files backend when you want:

• a network drive that lives inside the Everlock user model
• files reachable from the desktop file manager rather than through a web app
• file storage with history, on the same versioned store the sites, calendars, and mailboxes use

How it fits in the system

The files backend owns:

• collections and file resources
• WebDAV domain behavior, including locks
• authorization on http/files/<share>
• persistence in one store per configured share

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

Each share is a versioned store, so a file written over WebDAV is a commit. Clone the store and git log reads as the sequence of changes clients made; yesterday's version of a document is a git show away, and the share is subject to the same storage rules as everything else Everlock keeps.

Typical operator flow

1. enable the backend
2. create a share and assign a vhost
3. grant access to users or groups
4. mount the share from a file manager
5. drag files in

Pages

• WebDAV behavior and storage reference
• Getting started: Files backend
• Users, groups, and access control

Read next

• Versioned storage
• Calendar and Contacts — the other two DAV surfaces, sharing the same protocol machinery
• Architecture