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
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
The feature request sounds tiny: > A share on a `.local` host should appear in the file manager without anyone typing a URL. That is the user-facing requirement. The implementation turns into a small
One of the nice properties of self-hosted software is that it lives on your own network. One of the less nice properties is that you somehow have to find it there. When I added local discovery to Ever
The 0.13.0 release lets a photo instance catch up with a large library: captions run one photo after another, admin AI prompts no longer wait behind them, and each image instance gets job settings of
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
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
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
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
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:
Most self-hosting decisions are decisions about convenience. You move a service onto your own hardware, accept that you are now the person who patches it, and the worst realistic outcome is some downt