Everlock 0.14.0
The 0.14.0 release is the result of four test-coverage passes over the whole server, from 82 to 94 percent of its lines, and of the fixes they turned up: IMAP keeps its message numbers straight across
Documentation
Tag: git
What happens when your mailbox is a Git repository?
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
Forgetting, in a system built on remembering
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
Everlock 0.12.0
The 0.12.0 release brings workflows in line with forgejo-runner 13.2, keeps Immich phones in step with the server after an interrupted sync or a duplicate cleanup, closes a photo instance's Immich API
Your Backup Is a Git Clone. Until It Isn't.
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
If Everything Is in Git, Where Do the Access Logs Go?
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
Everlock 0.11.0
The 0.11.0 release puts a Windows binary on the download page, gives the built-in assistant a tool for every admin command, serves a page's Markdown source to clients that ask for it, and records when
The Dangerous Convenience of Implicit Ownership
Authorization systems often become complicated one convenience at a time. Everlock ran into a good example of this while working on repository permissions. The original rule sounded harmless:
Git over HTTP
Repositories are served over HTTPS as well as SSH, using git's standard smart HTTP protocol. Clone, fetch and push work with an unmodified git client. One backend serves three things on one host: the
The repository web UI
The host that serves [git over HTTP](/docs/git/http) also serves a browser surface over every hosted repository — one interface for the instance, not one per repository. It comes up with the backend:
Workflows
A push can start a build. Everlock speaks the runner protocol itself, so a stock [`forgejo-runner`](https://code.forgejo.org/forgejo/runner) registers against it and takes work — there is no separate
Getting started: Workflows
This guide runs a build on a push, locally: - start Everlock with git over HTTP, which serves the runner protocol too - create a repository and clone it over HTTP - register a `forgejo-runner` against