owenrees fa1fef7b62 Launch amendments: one login, crawler policy, and asset caching (#180)
* 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.
2026-11-17 12:55:47 +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%