An admin picks a technique theme and sees candidate endgames grouped by Key with counts. Expanding a family previews its boards without starting a puzzle, and selecting positions applies the theme in bulk as curated. Large families are paginated so a 600-endgame group stays usable, and curated links can be removed from the same surface. Removal is scoped to curated links, so derived and community links are never deleted by hand. Material themes are refused because derivation owns them. Closes #187
Chesstrainer
To start your Phoenix server:
- Run
docker compose up -dto run the development database - Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -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
- Official website: https://www.phoenixframework.org/
- Guides: https://phoenix.hexdocs.pm/overview.html
- Docs: https://phoenix.hexdocs.pm
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix