use defaultOverridePriority over mkDefault to fix acme error without cashing with settings from tests

This commit is contained in:
Kiara Grouwstra 2025-07-05 19:17:43 +02:00
parent 433d0dc278
commit baaa990513
Signed by: kiara
SSH key fingerprint: SHA256:COspvLoLJ5WC5rFb9ZDe5urVCkK4LJZOsjfF4duRJFU

View file

@ -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";