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: deployment
The embedded model
Every Everlock build embeds **MiniCPM-V 4.6 Thinking**. It is baked into the binary — the same model on every platform, in every container image, with no runtime switch and nothing to download separat
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
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