From baaa990513f08d2f2fe92e4acd00d3b546dc8fcb Mon Sep 17 00:00:00 2001
From: Kiara Grouwstra <kiara@procolix.eu>
Date: Sat, 5 Jul 2025 19:17:43 +0200
Subject: [PATCH] use defaultOverridePriority over mkDefault to fix acme error
 without cashing with settings from tests

---
 services/fediversity/default.nix | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/services/fediversity/default.nix b/services/fediversity/default.nix
index ced28bcb..70f84378 100644
--- a/services/fediversity/default.nix
+++ b/services/fediversity/default.nix
@@ -69,7 +69,9 @@ in
   config = {
     ## FIXME: This should clearly go somewhere else; and we should have a
     ## `staging` vs. `production` setting somewhere.
-    security.acme = lib.mkDefault {
+    # use a priority higher than mkDefault for panel deployment to work,
+    # yet lower than default so this will not clash with the setting in tests.
+    security.acme = lib.modules.defaultOverridePriority {
       acceptTerms = true;
       defaults.email = "something@fediversity.net";
       # defaults.server = "https://acme-staging-v02.api.letsencrypt.org/directory";