docs(#2502): meta flake input is the forge config repo, deploy overrides to local applied
This commit is contained in:
parent
27a099bb5b
commit
7df9f5d024
2 changed files with 24 additions and 1 deletions
|
|
@ -64,6 +64,11 @@ Two things live in the `agent-configs` Forgejo organization:
|
|||
approved history, the `failed/<id>` tag records the divergence).
|
||||
Repos stay private, so an agent can't read another
|
||||
agent's config. (Agents remain read-only collaborators on `core/meta`.)
|
||||
hive-c0re also references this repo as the agent's **persistent meta
|
||||
flake input** (`agent-<n>.url = git+http://<forge>/agent-configs/<n>.git`;
|
||||
see [approvals.md § Meta flake](approvals.md)), fetching it as the `core`
|
||||
user via a git credential helper that reads the live forge-core token —
|
||||
so the config lives on the forge, not a hand-synced local checkout.
|
||||
- The dashboard links each container's "config" anchor to this
|
||||
config repo, so operators can click straight from the SW4RM tab into
|
||||
the rendered repo without an extra `git` step.
|
||||
|
|
|
|||
Loading…
Reference in a new issue