| Filename | Latest commit message | Latest commit date |
|---|---|---|
d516bb890c
Each agent row on the hive dashboard, and the agent page's link menu, linked to the agent's forge profile and its config repo. Both are gone, with what only they used: - hive-agent no longer builds the two links, the `Forge` link kind, or the `forge_public_url` field of its state, and no longer reads `HIVE_FORGE_PUBLIC_URL`. The agent page's link menu and the dashboard row's icon strip (which skips a forge link an agent not yet rebuilt still sends) drop their forge handling. - hive-c0re's dashboard state no longer carries `forge_public_url`. - `HIVE_FORGE_PUBLIC_URL` is no longer forwarded to agents through the meta flake (the forwarded-variable list, its test fixture, the controller's settings and the VM test), so the next meta flake render differs by that one line. hive-c0re still reads it for the forge URL a hive publishes, so `swarm.forge.publicUrl` stays, with its description corrected. - The docs stop describing the links. |
||
| .. | ||
| src | ||
| testdata | ||
| Cargo.toml | ||
| README.md | ||
hive-meta-flake
The meta flake's flake.nix text: one nixosConfigurations.<agent> per agent,
each built from hyperhive's agent-base plus the agent's config input or
archetype.
Pure string rendering, with no IO and no environment reads. The caller passes
the hyperhive pin, the agents with their pins, and the values every agent
container gets. swarm-controller calls render_flake and reads the pins of the
flake it renders (pinned_rev). hive-c0re uses only the agent spec and port
helpers.
testdata/meta-flake.nix.in is the render for one archetype agent with a
placeholder for the hyperhive pin. A unit test keeps it equal to render_flake's
output, and the swarm-builder-offline VM test (nix/vm-tests/) serves it.
testdata/meta-flake-swarm.nix.in is the render for two archetype agents with
the forwarded values of a single-host swarm as @<NAME>@ placeholders, kept equal
by a unit test the same way. The full-setup VM test fills it in with the
controller's own settings and builds the agents' toplevels from it.