Idea
Currently outport share uses Cloudflare quick tunnels, which generate random ephemeral URLs (e.g., abc-def.trycloudflare.com). These work great for ad-hoc sharing but the URL changes every time.
Cloudflare also supports named tunnels which provide stable, predictable URLs (e.g., myapp-dev.yourdomain.com). These require a Cloudflare account, cloudflared tunnel login, and a domain managed by Cloudflare.
Use cases for stable URLs
- Webhook development (Stripe, GitHub, etc.) — don't have to update the webhook URL every session
- OAuth callback URLs — can be registered once
- Sharing with teammates — same URL every time
Open questions
- How much setup burden is acceptable? Named tunnels require account + auth + domain
- Should this be a separate provider, a flag on
outport share, or config in .outport.yml?
- Is there a discoverability concern with named tunnels (anyone with the URL can access your dev server)?
- How does this interact with the tunnel URL orchestration (
.env rewriting)?
Context
Quick tunnels are zero-config and cover most use cases. This would be an opt-in enhancement for developers who need URL stability.
Idea
Currently
outport shareuses Cloudflare quick tunnels, which generate random ephemeral URLs (e.g.,abc-def.trycloudflare.com). These work great for ad-hoc sharing but the URL changes every time.Cloudflare also supports named tunnels which provide stable, predictable URLs (e.g.,
myapp-dev.yourdomain.com). These require a Cloudflare account,cloudflared tunnel login, and a domain managed by Cloudflare.Use cases for stable URLs
Open questions
outport share, or config in.outport.yml?.envrewriting)?Context
Quick tunnels are zero-config and cover most use cases. This would be an opt-in enhancement for developers who need URL stability.