How muhammad-deve/goport works
GoPort exposes a developer’s local TCP service through a public HTTPS tunnel. The documented workflow is to authenticate, start a tunnel (optionally requesting or resetting a subdomain), route public traffic to the local app, monitor requests and tunnel status, and disconnect. The sampled Go client implements registration, yamux sessions, stream forwarding, and reconnection; the README describes server-side routing and PocketBase responsibilities. Backend, server, and landing-page internals were not sampled, so their relationships are shown only where documented.
Main entry points: server Tunnel server · goport.go Tunnel registration · backend Auth and subdomains · landing Traffic dashboard
Components 12
Tunnel client
- Go tunnel client
goport.go - Tunnel registration
goport.go - yamux streams
goport.go - Local stream proxy
goport.go
Public tunnel service
- Tunnel server
server - Auth and subdomains
backend - Public request routing
server
Web experience
- Traffic dashboard
landing - GoPort website
landing
Other components
- Developer
- Local application
- Public visitors
Connections 12
- Developer → Go tunnel client: starts tunnel
README.md - Go tunnel client → Tunnel registration: opens tunnel
goport.go - Tunnel registration → Tunnel server: registers over TCP
goport.go - Tunnel registration → Auth and subdomains: authenticates and requests URL
README.md - Tunnel server → yamux streams: creates yamux session
README.md - yamux streams → Local stream proxy: accepts streams
goport.go - Local stream proxy → Local application: forwards TCP traffic
goport.go - Public visitors → Public request routing: sends HTTPS requests
README.md - Public request routing → Tunnel server: routes through tunnel
README.md - Tunnel server → yamux streams: dispatches tunnel traffic
README.md - Developer → Traffic dashboard: monitors traffic
README.md - Developer → GoPort website: visits
README.md