seed a hyperhive/hyperhive mirror so update_meta finds it on a fresh swarm
This commit is contained in:
parent
dbdbed4dcc
commit
a6b5bafa83
1 changed files with 173 additions and 15 deletions
|
|
@ -251,6 +251,14 @@ environment (JSON-encoded `[{upstream, dest}]` list). It reads the list of
|
|||
the host the controller runs on: mirrors declared on any other host aren't
|
||||
seeded, and evaluation warns about them.
|
||||
|
||||
**The hyperhive mirror**: the same list carries `hyperhive/hyperhive`, from
|
||||
`services.hyperhive.deploy.forgejo.hyperhiveUpstream` (default
|
||||
`https://forge.darkest.space/hyperhive/hyperhive` on a host that runs the
|
||||
controller, unset elsewhere). The controller creates the mirror only when
|
||||
`hyperhive/hyperhive` doesn't exist, and it leaves a repo that exists but is
|
||||
not a mirror unchanged. `deploy.forgejo.mirrors` takes precedence for the same
|
||||
`dest`.
|
||||
|
||||
**General-purpose mirrors**: you can pre-seed any external repo as a
|
||||
pull-mirror via `services.hyperhive.deploy.forgejo.mirrors`:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue