Hey!
I noticed that the AI-Dock base already supports both persistent Cloudflare Tunnels via CF_TUNNEL_TOKEN and ephemeral Quick Tunnels.
One thing that still requires manual setup, though, is provisioning the persistent tunnel itself — creating the tunnel, configuring DNS/hostnames, and optionally setting up Cloudflare Access.
I maintain a small CLI called cfzt that automates that part:
https://github.com/casablanque-code/cfzt
For example:
zt up comfyui 8188 --hostname comfy.example.com
It creates and manages the Cloudflare-side resources and can handle the local tunnel lifecycle as well.
I'm not suggesting replacing the existing CF_TUNNEL_TOKEN or Quick Tunnel support. I was wondering if it would make sense to document cfzt as an optional workflow for users who want to provision and manage their own named tunnels without going through the Cloudflare Dashboard.
Happy to submit a small documentation PR if this is useful.
Hey!
I noticed that the AI-Dock base already supports both persistent Cloudflare Tunnels via
CF_TUNNEL_TOKENand ephemeral Quick Tunnels.One thing that still requires manual setup, though, is provisioning the persistent tunnel itself — creating the tunnel, configuring DNS/hostnames, and optionally setting up Cloudflare Access.
I maintain a small CLI called
cfztthat automates that part:https://github.com/casablanque-code/cfzt
For example:
It creates and manages the Cloudflare-side resources and can handle the local tunnel lifecycle as well.
I'm not suggesting replacing the existing
CF_TUNNEL_TOKENor Quick Tunnel support. I was wondering if it would make sense to documentcfztas an optional workflow for users who want to provision and manage their own named tunnels without going through the Cloudflare Dashboard.Happy to submit a small documentation PR if this is useful.