From e1ec1dfd6aa4f88377dafcd18c5ecc728e2dc74a Mon Sep 17 00:00:00 2001 From: V Date: Mon, 6 Jun 2022 12:45:46 +0200 Subject: fleet/hosts/trieste/web: fix homepage 404ing Unless Caddy recently changed how it resolves directives, this has been broken since the initial deployment. `error` directives are processed before `respond` directives[1], and unlike CSS, matcher precision does not impact directive precedence. Sticking a `route` directive around the two of them makes things work as expected. [1]: https://caddyserver.com/docs/caddyfile/directives#directive-order Change-Id: Ic05c6ba9a7143c3a58c2bf7ccd0498a7337257f8 --- fleet/hosts/trieste/web.nix | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'fleet') diff --git a/fleet/hosts/trieste/web.nix b/fleet/hosts/trieste/web.nix index 9b7752b..63d59d8 100644 --- a/fleet/hosts/trieste/web.nix +++ b/fleet/hosts/trieste/web.nix @@ -19,8 +19,10 @@ services.caddy.extraConfig = '' unfathomable.blue { import common - respond / "the depths await" - error 404 + route { + respond / "the depths await" + error 404 + } } ripple.unfathomable.blue { -- cgit 1.4.1