From 277045c1a1efcb1dd9c6d3c94ea067650b321614 Mon Sep 17 00:00:00 2001 From: Javier Cicchelli Date: Sun, 30 Aug 2026 23:01:48 +0200 Subject: [PATCH] Set the canonical site origin in the Website library target. The template's new `site.origin` key arrived empty, as bootstrap fills it in. Pointing it at the origin robots.txt and sitemap.xml already carry turns on the canonical and hreflang links, and the HTTPS redirect the production compose already trusts the forwarded proto for. --- .../Sources/Library/Public/Extensions/String+Constants.swift | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Services/Website/Sources/Library/Public/Extensions/String+Constants.swift b/Services/Website/Sources/Library/Public/Extensions/String+Constants.swift index d02a3fc..2ec035c 100644 --- a/Services/Website/Sources/Library/Public/Extensions/String+Constants.swift +++ b/Services/Website/Sources/Library/Public/Extensions/String+Constants.swift @@ -61,6 +61,6 @@ extension String { /// Bootstrap writes the canonical URL it prompts for here, leaving it empty for the placeholder. An empty or non-HTTPS origin disables /// the HTTPS redirect, which `https.trustForwardedProto` must enable besides — a `301` is cached for a long time, so it is never issued /// at a host nobody named. - public static let origin = "" + public static let origin = "https://ccn.rock-n-co.de" } }