setup-binaries.sh does not pre-populate CODEROOT/BUILDDIR/FORGE_TOKEN-deployer-context hero_proc secrets that deployer + downstream services require #67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
setup-binaries.sh installs the 35-component demo set and starts services, but does NOT pre-populate the hero_proc secrets that
hero_tfgrid_deployer_server(and likely other services) require at startup.Reproduced live at s158 admin VM bootstrap:
hero_tfgrid_deployer_serverpanicked on startup with:web server exited unexpectedly: build AppState failed: ForgeClient::connect_with_secret(\"deployer\", \"FORGE_TOKEN\"): forge environment error: PATH_CODE not in hero_proc: hero_proc secret CODEROOT exists but its value is empty.core/CODEROOTdid NOT fix it — the deployer reads the BARE keyCODEROOT(no context prefix), which is a separate slot fromcore/CODEROOT. Lesson #N: hero_proc supports both<key>and<context>/<key>slots and they are NOT the same.hero_proc secret set CODEROOT /home/driver/hero/code(bare key in default context) +BUILDDIR /home/driver/hero/build+FORGE_TOKEN <token> --context deployer.Fix candidates: (a) setup-binaries.sh pre-populates the canonical 9 secrets (CODEROOT, BUILDDIR, FORGEJO_TOKEN, FORGE_TOKEN, deployer/FORGE_TOKEN, TFGRID_NETWORK, TFGRID_NODE_IDS, TFGRID_MNEMONIC, HERO_PROXY_SEED_GATEWAY_LISTENER) at install time. (b) Document the required secret matrix prominently in DEPLOYMENT_NU_HERO_OS.md.
s158 also surfaced the bare-vs-prefixed slot ambiguity as a separate lesson worth adding to the herolib_base + hero_proc_secrets_and_meta skills.
Partial-progress note: hero_demo
8b8a27aadds one pre-population line tosetup-binaries.shforHERO_BOOKS_DEFAULT_REPOS, mirroring the existingEMBEDDER_MODEL_SIZEpattern just above it. This is the same shape #67 asks for, applied to a new variable.The broader request in #67 (pre-populating
CODEROOT,BUILDDIR,FORGE_TOKEN, etc.) stays open. The hero_books-only line shipped today is a useful template for the rest of the variables.