zachbg/tunnel repository overview

⁠Tunnel

Expose local Docker services to the internet. Supports SSH reverse tunnels (with auto-reconnect) and Cloudflare Tunnels — in one container.

⁠Why?

You need to show a client your local dev setup. Your home server is behind NAT. Your webhook endpoint needs to be publicly reachable. You don't want to configure port forwarding on your router or buy a static IP.

⁠Quick Start

⁠Cloudflare Quick Tunnel (instant, no account needed)

services:
  tunnel:
    image: zachbg/tunnel:latest
    environment:
      TUNNEL_TYPE: cloudflare
      LOCAL_HOST: webapp
      LOCAL_PORT: 8080

Gives you a random *.trycloudflare.com URL instantly.

⁠Cloudflare Named Tunnel (permanent, custom domain)

services:
  tunnel:
    image: zachbg/tunnel:latest
    environment:
      TUNNEL_TYPE: cloudflare
      CF_TOKEN: eyJhIjoiMj...

⁠SSH Reverse Tunnel

services:
  tunnel:
    image: zachbg/tunnel:latest
    volumes:
      - ~/.ssh/id_rsa:/key/id_rsa:ro
    environment:
      TUNNEL_TYPE: ssh
      SSH_HOST: myserver.com
      SSH_USER: root
      LOCAL_HOST: webapp
      LOCAL_PORT: 8080
      REMOTE_PORT: 9090

Your app is now accessible at myserver.com:9090.

⁠Environment Variables

⁠Common

⁠SSH Tunnels

⁠Cloudflare Tunnels

⁠Use Cases

• Webhook development: Expose local API to receive GitHub/Stripe webhooks
• Client demos: Share your local dev environment instantly
• Home server: Expose services behind NAT without opening router ports
• CI/CD callbacks: Allow external services to reach your build server