forked from Fediversity/Fediversity
reinstate acme settings needed by applications (#434)
closes #417 Reviewed-on: Fediversity/Fediversity#434 Reviewed-by: Valentin Gagarin <valentin.gagarin@tweag.io> Co-authored-by: Kiara Grouwstra <kiara@procolix.eu> Co-committed-by: Kiara Grouwstra <kiara@procolix.eu>
This commit is contained in:
parent
5520fa721b
commit
8a7984933d
1 changed files with 12 additions and 0 deletions
|
@ -65,4 +65,16 @@ in
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
|
|
||||||
|
config = {
|
||||||
|
## FIXME: This should clearly go somewhere else; and we should have a
|
||||||
|
## `staging` vs. `production` setting somewhere.
|
||||||
|
security.acme = {
|
||||||
|
acceptTerms = true;
|
||||||
|
# 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.
|
||||||
|
defaults.email = lib.modules.mkOverride 200 "something@fediversity.net";
|
||||||
|
# defaults.server = "https://acme-staging-v02.api.letsencrypt.org/directory";
|
||||||
|
};
|
||||||
|
};
|
||||||
}
|
}
|
||||||
|
|
Loading…
Add table
Reference in a new issue