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
Documentation
Tag: self-update
Self-hosted binary distribution and auto-update
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