From ec64da8620783d95cceea3654d1756b8cdc40697 Mon Sep 17 00:00:00 2001 From: iris Date: Wed, 27 May 2026 12:57:05 +0200 Subject: [PATCH] config: point forge_url at forge.darkest.space/hyperhive/hyperhive MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- config.toml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/config.toml b/config.toml index ebf33a4..d24e23d 100644 --- a/config.toml +++ b/config.toml @@ -34,7 +34,9 @@ palette = "catppuccin-mocha" accent = "amber" # Public-facing forge URL — surfaced in templates via -# `{{ config.extra.forge_url }}`. Update this when the canonical -# public hyperhive mirror lands; the current value is the operator's -# berlin.ccc.de instance (per the project README at that mirror). -forge_url = "https://git.berlin.ccc.de/vinzenz/hyperhive" +# `{{ config.extra.forge_url }}`. Points at the planned +# `forge.darkest.space` mirror (per mara on PR #1): not yet up, +# but will host `hyperhive/hyperhive` once it lands. Hardcoding +# 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"