-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add AutoTLS example #3103
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Marcin Rataj <[email protected]>
@MarcoPolo Is it a problem this PR upgrades the go to 1.23 in go.mod? I believe this happened due to dependency on p2p-forge |
ipshipyard/p2p-forge#29 should solve the build issue |
This comment was marked as outdated.
This comment was marked as outdated.
this also passes correct logger so debug messages from p2p-forge/client are printed correctly
this implements idea from libp2p/go-libp2p#3103 (comment) to ensure users who set up staging endpoint for testing are always aware fo it and never ship it to production
Yes. We can't do that until the Go team releases 1.24 |
implements idea from libp2p/go-libp2p#3103 (comment) to ensure users who set up staging endpoint for testing are always aware fo it and never ship it to production --------- Co-authored-by: Daniel Norman <[email protected]>
https://github.com/ipshipyard/p2p-forge/releases/tag/v0.2.2 main fix is ability to use the same go1.22 in examples as go-libp2p itself
285d38f
to
14e0d50
Compare
Pushed update to p2p-forge/client v0.2.2. It allows this PR to use the same go1.22 version in |
This adds an example showing how to use the p2p-forge client library with the AutoTLS backend to issue a wild card certificate.
Credits to @guillaumemichel for writing the initial code in this example.
Fix before merging