Skip to content

feat: support named Cloudflare tunnels#108

Open
OhThatMatt wants to merge 6 commits into
productdevbook:mainfrom
OhThatMatt:feat/named-tunnels
Open

feat: support named Cloudflare tunnels#108
OhThatMatt wants to merge 6 commits into
productdevbook:mainfrom
OhThatMatt:feat/named-tunnels

Conversation

@OhThatMatt
Copy link
Copy Markdown

PortKiller currently only supports Quick Tunnels (the throwaway *.trycloudflare.com URLs). This adds the other kind - named tunnels you create with cloudflared tunnel create and normally run with cloudflared tunnel run <name> from a terminal.

After this PR:

  • Tunnels from ~/.cloudflared/ and cloudflared tunnel list show up under Cloudflare Tunnels, grouped Running / Available / Managed Elsewhere.
  • Run / Stop buttons in the list, detail pane on the right with ingress, edge connections, and live logs.
  • Active ports in the All Ports view get a small globe badge linking to the public URL when a running tunnel routes to them.
  • "My Tunnels" section at the bottom of the menu bar dropdown.

One thing worth flagging: cloudflared supports multiple connectors per tunnel, so if a tunnel already has edge connections from another machine and no local ingress in config.yml, the Run button is hidden by default, running it from your laptop too would just create a competing connector. There's a "Run Anyway" in the detail view if you really want it.

Discovery is lazy - nothing runs cloudflared tunnel list until you open the Cloudflare Tunnels pane or the menu bar dropdown.

Closes #55.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Named / Authenticated Cloudflare Tunnels (Custom Domains)

1 participant