Enable localhost tunnel configurations in containerized-nginx setup.py #101
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
This was referenced Nov 24, 2024
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.
Some users opt to put huly behind a tunnel service implementation to avoid opening public-facing ports to their servers.
A tunnel service performs the task of routing external traffic directly to localhost:port of the huly instance.
A tunnel service also offers the option to provide an HTTPS endpoint to browsers without requiring it to be handled by the huly stack directly.
A few tunnel service examples are Cloudflare Zero Trust Tunnel, localhost.run, Tailscale Funnel, and many more anderspitman/awesome-tunneling.
This PR provides the configuration changes and documentation for how to implement a tunnel configuration with the huly project.