forked from Fediversity/Fediversity
use defaultOverridePriority over mkDefault to fix acme error without cashing with settings from tests
This commit is contained in:
parent
8ff5b87d00
commit
761d74a109
1 changed files with 3 additions and 1 deletions
|
@ -69,7 +69,9 @@ in
|
||||||
config = {
|
config = {
|
||||||
## FIXME: This should clearly go somewhere else; and we should have a
|
## FIXME: This should clearly go somewhere else; and we should have a
|
||||||
## `staging` vs. `production` setting somewhere.
|
## `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;
|
acceptTerms = true;
|
||||||
# use a priority more urgent than mkDefault for panel deployment to work,
|
# use a priority more urgent than mkDefault for panel deployment to work,
|
||||||
# yet looser than default so this will not clash with the setting in tests.
|
# yet looser than default so this will not clash with the setting in tests.
|
||||||
|
|
Loading…
Add table
Reference in a new issue