How wollomatic/socket-proxy works
Main Components Identification
a. Core Proxy Service
• Unix Socket Input (docker.sock or custom socket)
• TCP/Unix Socket Output
• Request Filter/Router
• Security Layer
b. Supporting Components
• Health Check Service
• Socket Watchdog
• Configuration Manager
TOP LAYER: Client Applications
↓
MIDDLE LAYER: Socket-Proxy Components
↓
BOTTOM LAYER: Unix Socket (Docker daemon or other)
Component Relationships
a. Input Flow:
• Client Applications → Socket-Proxy (TCP/Unix)
• Security Layer (IP/Hostname Verification)
• Request Filter (HTTP Method + Path Validation)
• Unix Socket Connection
b. Control Flow:
• Configuration Manager → All Components
• Watchdog → Socket Connection
• Health Check → Proxy Service
Specific Implementation Details
• Rectangles: Main processing components
• Diamonds: Decision points (security checks)
• Hexagons: Supporting services
• Blue: Core proxy functionality
• Red: Security components
• Green: Health/monitoring components
• Gray: External components (clients/socket)
Security Layer:
• IP/Hostname allowlist
• Default: 127.0.0.1/32
Request Filter:
• Method-specific regexp patterns
• Secure by default (deny-all)
Configuration:
• Command line parameters
• Environment variables
• Default values
Implementation Notes
a. Security-First Design:
• Multiple security checkpoints
• Default-deny approach
• Configuration validation
b. Monitoring Capabilities:
• Health check endpoint (optional)
• Socket watchdog
• Debug logging capability
c. Flexibility:
• Multiple input/output options
• Configurable security rules
• Various deployment scenarios