Everlock 0.7.0
The 0.7.0 release tightens who may do what. Access now derives solely from explicit grants, git repositories can hand out a contributor role that opens pull requests without touching branches, and vau
Documentation
The 0.7.0 release tightens who may do what. Access now derives solely from explicit grants, git repositories can hand out a contributor role that opens pull requests without touching branches, and vau
The 0.6.2 release brings captions to photo frames and a round of substance fixes: self-update no longer needs three binaries' worth of memory, image previews cache like the immutable content they are,
An e-paper frame on the wall shows a photo — and now, if you want, a line that says when and where it was taken. The photoframe endpoint draws a caption into the bottom-left corner of every frame it s
The 0.6.1 release finishes what 0.6.0 started. Administration now has a third outlet — a plain HTTP API with an OpenAPI document and a Swagger UI — generated from the same command registry as the SSH
The 0.6.0 release puts an AI assistant on equal footing with the admin console: every admin command is an MCP tool, authenticated with a new system-wide API key credential — and the whole admin surfac
Everlock now serves battery-powered e-paper picture frames. Point an [esp32-photoframe](https://github.com/aitjcize/esp32-photoframe) at an album and it wakes up, fetches one picture, and goes back to
Everlock's admin console now speaks MCP. The new `backend-admin-mcp` outlet exposes every admin command — around a hundred of them — as Model Context Protocol tools over streamable HTTP, so an AI assi
The 0.5.0 release makes HTTPS zero-config, turns the mail backend into a well-behaved internet citizen (outbound STARTTLS, inbound SPF/DKIM verification), and removes the last server restarts from eve
Everlock can replace its own binary in place — no SSH into the server, no manual service-restart dance, no downtime beyond the few seconds it takes to hand the sockets to the new process. There are tw
Everlock 0.4 adds the machinery to **distribute and self-update the native binary** from `everlock.sh` itself — while keeping the project's hard rule that Everlock is always *one self-contained binary
Everlock now hosts your passwords. The new **vault backend** (`backend-vault-http`) speaks the Bitwarden protocol, so the official Bitwarden clients you already use — desktop, browser extensions, mobi
The 0.3.0 release upgrades the Markdown-site templating engine to Tera 2 and refreshes the dependency baseline. Container images are published under the `0.3` tag family (`cr.everlock.sh/everlock:0.3-