Replies: 1 comment 1 reply
-
Personally, I use Certbot and ignore any built-in ACME support in any software.
Spam filter lookup lists will be stored in the config file and blow up its size. List of configuration keys I extracted from my database
Since the configuration file can (and will) be modified automatically and mdecimus adamantly refuses to add any options that could prevent it from being overwritten, I think any attempt to control the configuration file will fail and it's currently better to use the API instead. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks. Ended up finding acme.sh which also supports, unlike certbot, TLS-ALPN-01 challenges. I’ll investigate that approach some more, trying to keep things minimal, where possible… |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In Settings > Server > System > Local configuration keys on can put keys of values that should be in the local config file instead of in the database.
Is there a string that would result in the ACME certificates ending up in there, such that with a script they could be extracted for use by other software running on the system?
While on that subject: How much config data is actually stored in the database? Assume I’d simply were to add one line with "" or ".*" how big of a config.toml would I end up with?
And what would speak against it, besides maybe a somewhat slower reload/startup of the server?
The reason why I ask, is because such an approach would allow configuration with other tools than the built-in web interface, which in some cases might be desirable.
Beta Was this translation helpful? Give feedback.
All reactions