Public: anyone can read this; nobody can change it.
The quickstart says to run --first-admin beside the started forge, and shows spawning a child and making its admin from the same terminal #60
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Docs only (README "Run it"). Two gaps a new operator hits on current main:
shipped merged
Sign in to join this conversation.
Docs only (README "Run it"). Two gaps a new operator hits on current main:
--first-adminrefuses before the forge's first boot ("no forge database … start the forge once") and readsFORGE_DATA(andPORT/--urlfor the printed link), so the quickstart now says to run it beside the running forge with the same settings.POST /api/v1/forgesis a dry run unless"dryRun": false, the child is<name>--<host>with the parent's scheme and port (#47), its data is under$FORGE_DATA/children/, and its admin comes from--first-admin --child <name>or the one-timeclaimUrl.*.localhostneeds--resolvefor curl.Verified on the box, verbatim, on main 51b6c125
Default
PORT=3000, defaultdata/: start the forge →--first-admin(exit 0) →POST /api/v1/first-admin(rw token,isAdmin: true) →POST /api/v1/repos→git cloneover HTTP with the token →POST /api/v1/forges {"name":"kid","dryRun":false}(urlhttp://kid--localhost:3000) →--first-admin --child kid→ the child'sPOST /api/v1/first-adminvia--resolve(admin made). Before the first boot,--first-adminexits 1 with the line above. A password sign-up onPOST /api/v1/usersis refused (passkey_required); no sign-up path is described as making an admin. The Turnstile/closed-signup first-account lines are left as they are on main (#59 changes them).<!-- pipeline:validation -->
Validation
pipeline/validateon9ae578a9: pass in 7s — bun 1.3.14, CI-shaped env (scrubbed vars, runner PATH), exact check.yml shard + forge.json commands.bun install --frozen-lockfileforge.json check.fastcheck.yml gate (1) pull_requestcheck.yml gate (2) pull_requestcheck.yml gate (3) pull_requesttest output (failures, totals)