Allow TLS encryption at web server endpoint #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Secured mode can be activated and configured through the CLI.
Closed
|
Hi Martin, Sorry if I was a bit too vague/implicit in #5, but with not needing any support for client certificate validation I also meant that there's no need to integrate a HTTP server into bb-* processes at all. People can always use NGINX, stunnel, Traefik, Envoy, etc. to add TLS support to these services. This approach is also a bit more in line with other Go-based projects. For example, the Prometheus monitoring system also spawns a HTTP server exclusively. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Secured mode can be activated and configured through the CLI.
See #5.