forked from Fediversity/Fediversity
use defaultOverridePriority over mkDefault to fix acme error without cashing with settings from tests
This commit is contained in:
parent
433d0dc278
commit
baaa990513
1 changed files with 3 additions and 1 deletions
|
@ -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";
|
||||
|
|
Loading…
Add table
Reference in a new issue