feat: support named Cloudflare tunnels#108
Open
OhThatMatt wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PortKiller currently only supports Quick Tunnels (the throwaway
*.trycloudflare.comURLs). This adds the other kind - named tunnels you create withcloudflared tunnel createand normally run withcloudflared tunnel run <name>from a terminal.After this PR:
~/.cloudflared/andcloudflared tunnel listshow up under Cloudflare Tunnels, grouped Running / Available / Managed Elsewhere.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 listuntil you open the Cloudflare Tunnels pane or the menu bar dropdown.Closes #55.