owenrees 37e0ac8e56 Transactional mail, crawler metadata, and asset measurement (#179)
* Send transactional email from no-reply@mail.innersquare.app

Centralise the sender identity, reply-to address and SES configuration set in Chesstrainer.Mail so no notifier can drift. Add MAIL_REDIRECT_TO for smoke tests and a mix mail.check task that exercises the SES mailbox simulators, and document the setup in the deploy guide and .env.example.

* Tighten crawler metadata and keep play pages out of search

Canonical URLs no longer carry query strings, public pages get an OG image, WebSite JSON-LD and a per-page language, and the sitemap dates the landing page only. Play and guest-training routes are marked noindex so tens of thousands of near-identical pages stay out of the index.

* Measure built asset sizes with mix assets.sizes

Report raw, gzip and brotli sizes for built JS and CSS, and record the current numbers plus the board-code split recommendation in docs/assets.md.
2026-11-17 10:29:45 +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%