vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity
hyperhive/hive-meta-flake
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas 22e2d30581 pin internal/meta's hyperhive on the controller's rev and rebuild agents when it moves 
The swarm controller offers its own running rev (services.hyperhive.c0re.
hyperhiveRev) as the hyperhive pin of internal/meta and takes it only when
the forge compare API shows it descends from the committed pin; merges to
hyperhive main no longer move the pin, and the first commit pins main's head.
When a commit moves the pin, every placed agent gets a TriggerDeploy.

A deploy after a meta update no longer waits on it succeeding (after_any), so
a down builder does not hold back hives that render locally.
2026-10-24 21:13:24 +02:00
..
src pin internal/meta's hyperhive on the controller's rev and rebuild agents when it moves 2026-10-24 21:13:24 +02:00
Cargo.toml move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00
README.md move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00

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. hive-c0re and swarm-controller both call render_flake, so there is one renderer.