日本語版は準備中です。このページは英語版を表示しています。
First, keep two things apart: the engine is code (fetching, wave-height scoring, site generation); the data belongs to your instance (editions, the topic ledger, the track record, your config). The engine repo stores no instance data; everything you produce lives in your own data directory. Reading the public site needs no install at all — this page is for people who want to run their own.
git clone https://github.com/daiyanze/breaker-delta.git cd breaker-delta bun install bun run bundle # builds apps/cli/dist/breaker-delta.mjs — a single file
Every command runs through that single file; below it is called BD:
BD="bun apps/cli/dist/breaker-delta.mjs"
The fastest route is to copy the shape of the working data repo daiyanze/breaker-delta-data (or clone it and replace the data with yours). A data directory looks like this:
your-data/ config.yaml # your config (copy the engine's config.example.yaml and edit) editions/ # one result file per edition state/ # topic ledger, vocabulary and sitemap baselines (maintained by the program) track-record.md # the pick ledger and its 14-day review results
$BD --data-dir /path/to/your-data doctor # offline self-check $BD --data-dir /path/to/your-data scan --edition morning # fetch one edition's candidates $BD --data-dir /path/to/your-data publish --out site # build the static site
Next: tune sources and keywords to your field in Configuration, and put the site on GitHub Pages with Deploy Your Own.