Documentation
Everlock's mail server is deliberately boring at the edges. It receives mail over SMTP. Mail clients submit outgoing messages over SMTP submission. Apple Mail, Thunderbird, K-9 Mail, and Outlook read
Everlock is built around a simple promise: > History is part of the storage. A write does not silently replace the previous value. It creates another commit. That makes it possible to inspect how some
One of the appealing properties of storing application data in Git is that backups initially look almost too easy. If the repository contains the state, then make another copy of the repository. git c
Everlock stores its state in Git repositories. That is a useful constraint. Files are versioned. Changes have history. Replication can use Git. Backups can use Git. A repository can be inspected witho
"Everything is Git" describes the architectural rule behind Everlock. This article is the more mechanical version of that idea. What does it actually mean to build application storage on top of bare G
Everlock starts with a fairly unreasonable constraint: > Everything that matters should live in Git. Not just the source code for Everlock. The data managed by Everlock. Photos. Calendars. Configurati
The 0.8.0 release adds file shares: a versioned store mounted as a network drive over WebDAV, from Finder, Windows Explorer, a Linux file manager, or `rclone`. Every change is a commit, so a share's h
This page covers Everlock's WebDAV behavior and the storage model behind it. - served through `frontend-http` - multi-share and multi-vhost, each share on its own mount path - one dedicated `versioned
A repository that collects build artifacts, uploads, or generated data grows forever, and a large file committed once keeps costing disk long after it was deleted. Everlock can bound that: a repositor
Versioned storage is Everlock's internal persistence primitive. Every backend that needs to store state — site content, user records, mail, uploaded files, system configuration — uses it. It is a key-
Everlock's architecture is built on a small set of reusable primitives. These are not optional conveniences; they are the common foundation that backend families are expected to reuse. Git-backed stor
