Fix certmagic usage. Fixes https://github.com/joohoi/acme-dns/issues/337 #351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No separate certmagic cache needed. Default config and cache are sufficient to handle the certificates for the HTTP API.
Updated to certmagic v0.20.
Issue of double cache was introduced by 27e8251 (from #334), when updating certmagic to v0.17, and reported in #337
Also maybe related to #347, no cert, no update, no txt record.
Succesfully Tested (Ubuntu 22.04 LTS):
Built on Ubuntu 22.04 LTS:
GOPATH=/tmp/go-acme-dns CGO_ENABLED=1 go build
(CGO_ENABLED for sqlite)Installation on Ubuntu 22.04 LTS: