hyperhive/website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

config: point forge_url at forge.darkest.space/hyperhive/hyperhive

Browse source 
mara on PR #1: "you can hard code upstream repo URL with
forge.darkest.space - that does not exist _yet_, but will have
hyperhive/hyperhive at some point". Hardcoding the future URL
now means no template / config churn when the mirror goes live —
only DNS + web wiring on the operator's side.
This commit is contained in:
iris 2026-05-27 12:57:05 +02:00
parent b82a2ca1b3
commit ec64da8620
1 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
config.toml
View file

@ -34,7 +34,9 @@ palette = "catppuccin-mocha"
accent = "amber" accent = "amber"
# Public-facing forge URL — surfaced in templates via # Public-facing forge URL — surfaced in templates via
# `{{ config.extra.forge_url }}`. Update this when the canonical # `{{ config.extra.forge_url }}`. Points at the planned
# public hyperhive mirror lands; the current value is the operator's # `forge.darkest.space` mirror (per mara on PR #1): not yet up,
# berlin.ccc.de instance (per the project README at that mirror). # but will host `hyperhive/hyperhive` once it lands. Hardcoding
forge_url = "https://git.berlin.ccc.de/vinzenz/hyperhive" # the future URL means no template churn when it goes live —
# only DNS / web wiring on the operator's side.
forge_url = "https://forge.darkest.space/hyperhive/hyperhive"