owenrees 9e76045862 Automate, verify, and ship database backups off-box (#145) (#152)
The VPS now takes a daily logical dump, verifies it, encrypts it, and hands
it to a workstation; a monthly drill proves the archive restores.

- deploy/backup: pg_dump -Fc plus pg_dumpall --globals-only, pg_restore -l
  and globals-role checks before anything is promoted, row counts for the
  drill, sha256, age encryption into offsite/, retention (3d plaintext,
  14d encrypted, 5 pre-deploy sets), JSON logging and a healthchecks.io
  heartbeat
- systemd service and timer (03:15 UTC, Persistent, jittered) plus an
  OnFailure unit that logs a distinct event
- deploy/activate takes a pre-deploy dump after extracting and before
  flipping current, because migrations run in ExecStartPre; a failed dump
  aborts the activation, with SKIP_PRE_DEPLOY_BACKUP=1 as the escape hatch
- deploy/workstation/backup-pull: rsync the encrypted archives over SSH,
  verify by decrypting and checking the inner sha256, retain 7d/4w/6m, and
  fail when the newest archive is older than 48h
- deploy/workstation/backup-drill: restore the newest archive into a
  throwaway postgres:18.6, replay the globals dump as the same superuser,
  assert both roles, compare users/endgames/attempts, and append the result
  to drills.log
- user units for the daily pull and monthly drill, with a shared OnFailure
  alert template
- docs: install, key handling, retention, restore, disaster recovery, a run
  by hand section, monitoring and troubleshooting

Verified against production: the first backup completed and pinged the
heartbeat, the pull verified the archive, and the drill restored
users=1 endgames=39 attempts=0, matching the live database.
2026-11-11 22:59:54 +01:00
2026-11-09 20:52:37 +01:00
2026-06-20 19:08:18 +02:00

Chesstrainer

To start your Phoenix server:

  • Run docker compose up -d to run the development database
  • Run mix setup to install and setup dependencies
  • Start Phoenix endpoint with mix phx.server or inside IEx with iex -S mix phx.server

Now you can visit localhost:4000 from your browser.

Ready to run in production? Please check our deployment guides.

Local tablebases (optional)

Positions with five or fewer pieces are answered locally from Syzygy tablebases when TABLEBASE_PATH points at a directory of .rtbw/.rtbz files; otherwise lookups fall back to Lichess.

mix tablebase.fetch --path /path/to/syzygy/3-4-5   # once per host (~939 MB)
export TABLEBASE_PATH=/path/to/syzygy/3-4-5        # set per environment

On the production VPS the directory is /opt/chesstrainer/tablebases, owned by the chesstrainer user. Set TABLEBASE_PATH in /etc/chesstrainer/env and restart the service; the value is read at boot.

See docs/tablebases.md for the full reference — dev vs VPS paths, mix tablebase.check, and boot logging.

Logging

Production logs are one JSON object per line so they can be filtered with journalctl and jq; development and test keep the readable formatter. See docs/logging.md for the line shape, redaction rules and the background-work audit, and deploy/README.md for the VPS runbook.

Learn more

S
Description
No description provided
Readme
1.7 MiB
Languages
Elixir 83.4%
HTML 7%
Shell 3.6%
CSS 3%
JavaScript 2%
Other 0.9%