IPv4 and IPv6
Every Everlock frontend listens on whatever set of addresses you give it. This page covers the three shapes that set can take — one family, both families on every address, and both families on chosen
Documentation
Tag: operations
Self-update
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
Server settings
`/server settings` in the [admin console](/docs/admin) is the single entry point for runtime-tunable, server-wide values. Settings live in the `everlock-system` store (`settings.json`), so every chang
Deployment
Everlock is one self-contained binary with the model embedded — nothing to assemble, no runtime dependencies, and **storage is always just filesystem access**: a single data directory of git-backed fi
systemd with socket activation
This is a full setup for a native Linux host. systemd binds each listening socket and passes it to Everlock, which gives you two things: an **unprivileged process** (systemd binds the low ports, so Ev
Known issues
Rough edges we've run into ourselves, collected here so you don't have to rediscover them. Each entry lists the **error** you'll see, **what to do**, and a short note on **why it helps** so the fix is