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
Suggestion:
I think that it's a good idea to support tailscale client flags via env vars.
This will allow the use of the node as an exit-node for example.
The text was updated successfully, but these errors were encountered:
we've exposed the new-ish web UI in golink to allow managing the Tailscale part of it remotely. Instructions for how to enable that on your tailnet can be found here. Once you've done that, you can go to http://go:5252/, login (again), and then manage several aspects of the device including making it an exit node. We're working on adding more stuff to that web UI over time.
There are still other valid reasons to potentially expose some setting via environment variables, but I suspect we'd probably add support for the newer JSON config before that, which is the direction some of our other containers are moving in (see #10993)
Suggestion:
I think that it's a good idea to support tailscale client flags via env vars.
This will allow the use of the node as an exit-node for example.
The text was updated successfully, but these errors were encountered: