ACME Server TLS example with Let's Encrypt and certmagic #125
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.
Full example for a TLS setup with Fuego. This example should get you very close to a production setup with HTTPS (and HTTP/2), automatic TLS certificates (with auto-renew) and HTTP to HTTPS redirect.
Key points:
tls.Config
fromcertmagic
on the Fuego's underlyinghttp.Server
This is examples is meant to be run on server that has a real DNS record pointing to it, with ports 80 and 443 opened. You need to provide the domain name and email address using flags.
While initially I was considering autocert I found to
certmagic
from Caddy to be more powerful.