vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(ci): fix stale nix option namespace and ensure_mirrors file path

Browse source
This commit is contained in:
iris 2026-08-15 12:17:53 +02:00 • committed by mara
commit 8361d3f6a1
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/ci.md
View file

@ -5,7 +5,7 @@ executing CI jobs from `.forgejo/workflows/ci.yml` on every PR.
## For operators
**Enabling it is one line**: `services.hyperhive.forge.ci.enable = true`
**Enabling it is one line**: `services.hyperhive.swarm.forge.ci.enable = true`
in the host NixOS config. No manual token provisioning — hive-c0re
registers the runner with the forge automatically.
@ -74,9 +74,9 @@ slow); run those manually before pushing Rust changes.
The internal forge is always present (mandatory), so the runner always has a
hive-forge instance to register against — nothing extra to enable beyond
`services.hyperhive.forge.ci.enable = true` (see *For operators* above).
`services.hyperhive.swarm.forge.ci.enable = true` (see *For operators* above).
Optional tuning: `services.hyperhive.forge.ci.name` (runner name in forge
Optional tuning: `services.hyperhive.swarm.forge.ci.name` (runner name in forge
admin panel), `concurrency` (parallel job capacity), `labels` (workflow
targeting), `jobTimeout` (per-job wall-clock cap, default `"1h"`, Go duration
string e.g. `"3h"` — a job that exceeds it is killed so a hung or runaway
@ -126,7 +126,7 @@ When `forge.ci.enable` is set, hive-c0re auto-seeds an
external DNS on the CI critical path.
The mirror is seeded by **hive-c0re** itself during its forge
provisioning sweep (`forge.rs::ensure_mirrors`). The nix module
provisioning sweep (`forge/repos.rs::ensure_mirrors`). The nix module
forwards the effective mirror list as `HYPERHIVE_FORGE_MIRRORS` in the
`hive-c0re` service environment (JSON-encoded `[{upstream, dest}]`
list). hive-c0re already holds the admin token for the rest of the
@ -134,10 +134,10 @@ forge provisioning sweep (orgs, agent accounts, etc.), so mirror
seeding lives in the same place rather than a separate host-side unit.
**General-purpose mirrors**: you can pre-seed any external repo as a
pull-mirror via `services.hyperhive.forge.mirrors`:
pull-mirror via `services.hyperhive.swarm.forge.mirrors`:
```nix
services.hyperhive.forge.mirrors = [
services.hyperhive.swarm.forge.mirrors = [
{ upstream = "https://github.com/actions/checkout"; dest = "actions/checkout"; }
{ upstream = "https://github.com/example/tool"; dest = "mirrors/tool"; }
];