Add target service variables to support https+insecure mode #14
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.
Summary
Allows setting specific target mode and specific serving port as they're allowed to be changed in CLI.
What changed
<mode>:<port>
<mode>://localhost:<port>
syntax when using Serve.TAILSCALE_TARGET_MODE
andTAILSCALE_TARGET_PORT
variables forJustification
To enable supporting use cases like hosting a UniFi controller's web portal on a Tailnet which is normally self-signed https on 8443 (#13) and also to support allowing to set a custom port number within the allowed ones for the endpoint (docs).
Breaking change(s)
TAILSCALE_SERVE_PORT
now addresses port number for the endpoint that is exposed on the Tailnet instead of the target service's port number.