You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The prompt and case handling for NGINX_LOCALHOST_BEHIND_TUNNEL treat empty or invalid input via the default '*' branch, which behaves like a 'no' response but emits a confusing message. Consider consolidating the 'no' and default cases and clarifying the prompt defaults.
read -p "Do you tunnel inbound public traffic directly to localhost:port? (y/N): " NGINX_LOCALHOST_BEHIND_TUNNEL
case"$NGINX_LOCALHOST_BEHIND_TUNNEL"in
[Yy]* )
SERVER_ADDRESS="${DOMAIN_NAME}"
;;
[Nn]* )
SERVER_ADDRESS="${DOMAIN_NAME}:${NGINX_SERVICE_PORT}"
;;
* )
echo"Proceeding without localhost tunnel configuration"
SERVER_ADDRESS="${DOMAIN_NAME}:${NGINX_SERVICE_PORT}"
;;
esac
The README refers to 'setup.py' in the instructions, but the script is actually named 'setup.sh'. Update the documentation to match the actual script name to avoid user confusion.
### Run setup.py and provide your configuration
This example will configure Huly to be served publicly over SSL at `https://huly.example.com:12345`\
You need to choose your own hostname and port number.
~/huly-selfhost/nginx$ ./setup.sh
Enter the domain name: huly.example.com
Enter the port you want nginx to expose: 12345
Do you run behind SSL proxy (did you setup HTTPS)? (Y/n): y
Do you tunnel inbound public traffic directly to localhost:port? (y/N): n
Setup is complete. Run 'docker compose up -d' to start the services.
This file contains hidden or 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
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.