How tobychui/zoraxy works
Main Components Identification
The system should be divided into these major components:
a) Core Proxy Services:
• Dynamic Proxy (HTTP/2)
• Stream Proxy (TCP/UDP)
• WebSocket Proxy
• Forward Proxy
• Reverse Proxy
b) Security Layer:
• Authentication System
• Access Control (Blacklist/Whitelist)
• TLS/SSL Management (ACME)
• GeoIP Filtering
c) Management Interface:
• Web UI
• API Endpoints
• Configuration Management
d) Additional Services:
• Web SSH Terminal
• Network Utilities
• Monitoring System
• Global Area Network Controller
[Client Requests] → [Load Balancer/Entry Point]
• ↓
[Security Layer: Auth, ACL, GeoIP]
• ↓
[Core Proxy Services] ←→ [Configuration Management]
• ↓ ↑
[Backend Services] ←→ [Monitoring & Analytics]
Specific Implementation Details
Key relationships:
• ACME certificate management with DNS providers
• WebSocket automatic protocol upgrade
• Authentication flow with external systems
• Load balancing and routing mechanisms
• Monitoring and analytics data flow
Important Architectural Patterns to Highlight
• Modular design (evident from the /mod directory structure)
• Plugin architecture for various proxy types
• Middleware pattern for request processing
• Event-driven architecture for monitoring
Technical Stack Indicators
• Go runtime
• HTTP/2 support
• WebSocket protocol
• TCP/UDP protocols
• ZeroTier integration
• ACME/Let's Encrypt
Integration Points
Connections with:
• External DNS providers
• Authentication systems
• Backend services
• Monitoring systems
• ZeroTier network