the rendered meta flake pins hyperhive by forge URL and follows its nixpkgs
This commit is contained in:
parent
6ea13c02e3
commit
bb13909d8e
8 changed files with 135 additions and 153 deletions
|
|
@ -28,8 +28,8 @@ Where it runs and how it's enabled: [`services.md`](services.md#builder).
|
|||
3. The builder runs `nix build` of `nix/builder/check-flake`'s `check` output
|
||||
with every input overridden:
|
||||
- `hyperhive` and `nixpkgs`: the sources the builder's own host was
|
||||
deployed with, the same two a hive on that host renders into its meta
|
||||
flake (`c0re.hyperhiveFlake`, `c0re.nixpkgsFlake`).
|
||||
deployed with (`c0re.hyperhiveFlake`, `c0re.nixpkgsFlake`). A hive's meta
|
||||
flake pins `hyperhive` by forge URL and rev instead.
|
||||
- `hyperhive-docs`: the `docs/` source a hive on that host renders into its
|
||||
meta flake (`c0re.hyperhiveDocs`). The check sets
|
||||
`services.hyperhive.agent.docs.source` from it, as the meta flake does,
|
||||
|
|
|
|||
Loading…
Reference in a new issue