seed a hyperhive/hyperhive mirror so update_meta finds it on a fresh swarm
This commit is contained in:
parent
dbdbed4dcc
commit
a6b5bafa83
2 changed files with 173 additions and 15 deletions
|
|
@ -85,6 +85,21 @@ services.hyperhive = {
|
|||
Run `nixos-rebuild switch --flake .#my-host`. The swarm UI then answers at
|
||||
`https://<swarm.domain>/`.
|
||||
|
||||
### The hyperhive mirror
|
||||
|
||||
The swarm controller pins the hive's flake inputs to a commit of hyperhive on
|
||||
the swarm's own forge, so the forge needs a `hyperhive/hyperhive` repo before
|
||||
the first agent builds. On a host that runs the forge and the controller,
|
||||
the controller creates it as a pull-mirror of
|
||||
`https://forge.darkest.space/hyperhive/hyperhive`. You run no extra step.
|
||||
|
||||
| option | what it does |
|
||||
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `deploy.forgejo.hyperhiveUpstream` | The clone URL the mirror pulls from. Set another URL to mirror a fork, or `null` to seed nothing and provide the repo yourself. The controller creates the mirror only if `hyperhive/hyperhive` doesn't exist, so a repo already there stays as it is. |
|
||||
|
||||
Without the repo, the first agent's `update_meta` job step fails with
|
||||
`hyperhive/hyperhive is empty or absent on the swarm forge`.
|
||||
|
||||
## Everything else is optional
|
||||
|
||||
Leave the other options at their defaults until you need them:
|
||||
|
|
|
|||
|
|
@ -149,7 +149,10 @@ swarmctl agent create iris --hive firsthive
|
|||
|
||||
The controller provisions iris's identity, forge user and config repo
|
||||
(`agent-configs/iris`, from the default template), then has the hive build
|
||||
and start the container. It returns once the scheduler queues the job — watch the
|
||||
and start the container. The hive builds from a copy of hyperhive on the swarm's own forge: the
|
||||
controller mirrors it there as `hyperhive/hyperhive` on a fresh swarm, so the
|
||||
first agent needs no extra step (see
|
||||
[`nixos.md`](nixos.md#the-hyperhive-mirror)). It returns once the scheduler queues the job — watch the
|
||||
swarm UI's job view for progress.
|
||||
|
||||
Later config changes are PRs on `agent-configs/iris`; you merge them on the
|
||||
|
|
|
|||
Loading…
Reference in a new issue