How night-days/edgetunnel works
edgetunnel is a Cloudflare Workers/Pages edge tunnel with an admin panel and client-facing proxy and subscription features. Users connect through the deployed worker; the README documents protocol handling, subscription generation, configurable proxy paths, and administration. The implementation is a single large _worker.js, so distinct product responsibilities share that path. The excerpts show KV-backed logging/configuration and optional Telegram notification behavior; other feature boundaries and dispatch details are documented but not visible in the sampled code.
Main entry points: _worker.js Request handler
Components 13
Edge runtime
- Request handler
_worker.js
Management
- Admin panel
_worker.js - Runtime configuration
_worker.js - Logs and statistics
_worker.js - Cloudflare KV
- Telegram notifications
Tunnel and connectivity
- Protocol ingress
_worker.js - Traffic forwarding
_worker.js - Proxy selection
_worker.js - Subscription generator
_worker.js - Cloudflare network
- External proxies
Other components
- Clients and admins
Connections 13
- Clients and admins → Request handler: send requests
README.md - Request handler → Protocol ingress: handles protocols
README.md - Request handler → Subscription generator: generates subscriptions
README.md - Request handler → Admin panel: serves admin
README.md - Request handler → Traffic forwarding: forwards traffic
README.md - Request handler → Proxy selection: selects proxy
README.md - Request handler → Runtime configuration: reads settings
README.md - Request handler → Logs and statistics: records activity
_worker.js - Logs and statistics → Cloudflare KV: writes logs
_worker.js - Runtime configuration → Cloudflare KV: reads configuration
_worker.js - Logs and statistics → Telegram notifications: sends notifications
_worker.js - Proxy selection → External proxies: connects through
README.md - Traffic forwarding → Cloudflare network: uses edge platform
README.md