* lesson library shown as com,ing soon. re-enable learngin strip * replace learning strip text with a lasker quote * remove admin login endpoint * fix crawler directives and prelaunch login - noindex the authenticated scope and the 404 catch-all, and cover the mailing-list confirmation redirect - emit noindex, nofollow from the robots meta and /health, and assert public pages stay indexable and followable - stop inventing lastmod values in the sitemap - log in through /users/log-in during prelaunch now that the admin login endpoint is gone; drop create_admin/2 and its orphaned tests * update caching length to 1 year - name change will invalidate cache * remove logger * fix tablebase path breaking tests * test: check cache headers without requiring built assets CI's test job does not run mix assets.build, so /assets/css/app.css is a 404 there. Committed piece art is already content-hashed and takes the same Plug.Static cache option, so the test no longer needs a build step and passes on a fresh checkout.
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