use tailscale cert manager with tailscale-proxy command #57
Conversation
Instruct caddy to use the tailscale cert manager. Also add a --debug flag to enable debug logging with the tailscale-proxy command. Also remove a lingering `auto_https off` config in one of our examples. Fixes #27 Signed-off-by: Will Norris <will@tailscale.com>
| @@ -216,6 +227,17 @@ func cmdTailscaleProxy(fs caddycmd.Flags) (int, error) { | |||
| }, | |||
| AppsRaw: appsRaw, | |||
| } | |||
| if debug { | |||
There was a problem hiding this comment.
Question: is the caddy config generated here persisted across restarts? (If it is, then users would have no way to unset the debug flag except for by deleting the config)
There was a problem hiding this comment.
no, this config is entirely in memory. It's not persisted anywhere.
In hindsight, I'm not actually sure how useful this tailscale-proxy subcommand really is compared to just creating a pretty simple caddyfile that does the same thing. It was something I added pretty on, mostly just to see if I could 🤷🏻
There was a problem hiding this comment.
would the proxy subcommand be useful for the Dockerfile? #14
There was a problem hiding this comment.
yeah, possibly. If the Dockerfile just provided a caddy binary with the tailscale plugin compiled in, then you could use that to run the proxy. I'll go ahead and add that to the v1 milestone... seems worth doing.
Instruct caddy to use the tailscale cert manager. Also add a --debug flag to enable debug logging with the tailscale-proxy command.
Also remove a lingering
auto_https offconfig in one of our examples.Fixes #27