Prediction Stack docs
 v1.0.0
Live app Get help
● Ship · New releases

Updating
keep your files.

There is no automatic updater. A new release is new files; your own state lives in a few files you must keep.

01Files that are yours

FileWhat it holdsIn git?
admin/.envADMIN_SECRET_KEY and admin settingsNo. Back it up.
admin/data/admin.sqliteEvery admin setting, members, audit log, history, encrypted secretsNo. Back it up with .env.
config/public.jsonYour public settingsYes
scanner/data/pairs.jsonlThe pair database with your review decisionsYes
board.json, crossvenue-diag.json, tape.jsonThe latest dataYes, regenerated by every run
.github/workflows/refresh.ymlYour schedule, if you turned it onYes

02Update steps

  1. Back upStop the admin and copy admin/.env and admin/data/ somewhere safe.
  2. PullGet the refresh job's latest commits with git pull.
  3. Bring in the release on a branchCopy the new files over your working copy. Keep your config/public.json and pairs.jsonl; re-apply your schedule line if refresh.yml changed.
  4. Reinstall the admincd admin && npm install && npm test
  5. Start and checkStart the admin and open Status. It rewrites config/public.json on start.
  6. ShipRead the Changelog, commit, push, and let the next refresh run confirm the job still passes.

03Coming from an earlier copy to 1.0.0

  • The vendored Admin Kit was refreshed (still 0.3.0, asynchronous storage) and the product routes moved from admin/src/server.ts to admin/src/app.ts. If you changed server.ts, move your routes to app.ts and await the Kit's authenticate() and audit(). Your admin/.env and admin.sqlite keep working.
  • refresh.yml now passes the POLYGON_RPC_URL secret to the tape step. If you edited the workflow, re-apply your schedule on top of the new file.
  • config/public.json keeps schema mikodes-prediction-public/1: no change needed.

04When the matcher version changes

Every pair you already decided is flagged for re-review on the next run and leaves the priced set until you look at it again. Your decision is kept, not overwritten.

05When the public schema changes

config/public.json carries schema: "mikodes-prediction-public/1". Pages that do not know a new schema ignore the file and use their defaults, so deploy the pages and the new file together.