Documentation — Home services
The files, the settings and the verification commands.
The systemd units
Each service is a oneshot unit triggered by a timer, with User=athena and an
absolute path. Two traps to avoid:
%hdoes not mean what you think. In a unit withoutUser=, systemd runs as root and%his/root. That is the mistake I made, and the service journal shows it:Unable to locate executable '/root/Documents/...'.HOMEis not necessarily readable. A service reading a database in/home/athenamust run asathena, or use a neutral folder such as/var/lib.
Loopback
A service listening on 127.0.0.1 is only reachable from the machine. That is
the default setting, and it is better than a tunnel. The status page listens on
127.0.0.1:8081, Grafana on 127.0.0.1:3000.
Monitoring
One sample per minute, a SQLite database, and alerts only on a change of state. Thresholds live in a file, not in the code.
Backups
vault_backup.sh # commit, bundle, verify the bundle, checksums
git_sync.sh # commit and push the layer
The bundle is verified before being declared successful. A corrupted bundle fails the script; it does not silently replace the previous one.
Verification lives in the script, not in the documentation: the script decides, and that is why it can be trusted.