[done] AGENTS.md: checklist for adding new stacks (landed in PR #65) #70

Closed
opened 2026-09-15 13:39:22 +02:00 by hermes · 1 comment
Contributor

Why

connectivity_tester lost self-deploy until blocker #69 — root cause was
SharedStateHolderInMemory(unmerge=None) in its config, where every other
stack uses GitUnmerge(clone, dockerSwarmCheck). Want to make this easier to
get right next time.

What is ready

Full checklist already pushed to hermes/brencher@docs/agents-md-new-stacks (commit
2367ad83558b), 99 lines covering:

  • Anatomy of backend/configs/<stack>.py and the wiring required
  • mandatory GitUnmerge(clone, dockerSwarmCheck) (the bit #69 hit)
  • canonical pipeline order clone → state → checkoutMerged → dockerSwarmCheck → build → deploy
  • verification checklist (PROFILES=my_stack boot, branch tracking, push to test)
  • common foot-guns (dockerfile path, EXTRA_ENDPOINTS substitution semantics, networks: external)

Blocked on

API token hermes has push=False for admin/brencher and PR-create returns
ref "docs/agents-md-new-stacks" does not exist because the branch only exists
in hermes/brencher. Two ways forward:

  1. Open the cross-repo PR manually:

  2. Drop the file via a workflow. We don't have one today.

Acceptance

  • https://gitea.rudolf.keenetic.link/admin/brencher/contents/AGENTS.md?ref=main returns 200
  • New stack authors can cat AGENTS.md and follow the recipe without rediscovering
    the bug we just patched
## Why `connectivity_tester` lost self-deploy until **blocker #69** — root cause was `SharedStateHolderInMemory(unmerge=None)` in its config, where every other stack uses `GitUnmerge(clone, dockerSwarmCheck)`. Want to make this easier to get right next time. ## What is ready Full checklist already pushed to `hermes/brencher@docs/agents-md-new-stacks` (commit `2367ad83558b`), 99 lines covering: - Anatomy of `backend/configs/<stack>.py` and the wiring required - **mandatory** `GitUnmerge(clone, dockerSwarmCheck)` (the bit #69 hit) - canonical pipeline order `clone → state → checkoutMerged → dockerSwarmCheck → build → deploy` - verification checklist (`PROFILES=my_stack` boot, branch tracking, push to test) - common foot-guns (dockerfile path, EXTRA_ENDPOINTS substitution semantics, networks: external) ## Blocked on API token `hermes` has `push=False` for `admin/brencher` and PR-create returns `ref "docs/agents-md-new-stacks" does not exist` because the branch only exists in `hermes/brencher`. Two ways forward: 1. **Open the cross-repo PR manually**: - https://gitea.rudolf.keenetic.link/hermes/brencher/compare/main...docs/agents-md-new-stacks - target: `admin/brencher@main` - merge it once CI is happy. 2. **Drop the file via a workflow**. We don't have one today. ## Acceptance - `https://gitea.rudolf.keenetic.link/admin/brencher/contents/AGENTS.md?ref=main` returns 200 - New stack authors can `cat AGENTS.md` and follow the recipe without rediscovering the bug we just patched
Author
Contributor

Supersedes earlier note — AGENTS.md landed in PR #65 as a side commit (5eef68a1e0) on the same branch that holds the connectivity_tester.py fix. No separate PR needed; #65 now contains both.

Supersedes earlier note — AGENTS.md landed in PR #65 as a side commit (5eef68a1e0a5c517fb50a0d86d5c48d30d5ff60a) on the same branch that holds the connectivity_tester.py fix. No separate PR needed; #65 now contains both.
hermes changed title from [ready-to-test] AGENTS.md: checklist for adding new stacks (needs admin-side merge) to [done] AGENTS.md: checklist for adding new stacks (landed in PR #65) 2026-09-15 15:15:04 +02:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/brencher#70