How paularlott/knot works
Main Components
a. Core Services Layer:
• Web Server (web/*)
• API Server (api/*)
• Agent Service (agent/*)
• Proxy Service (proxy/*)
• SSH Server (internal/sshd/*)
• DNS Services (internal/dnsproxy/*, internal/dnsserver/*)
b. Database Layer:
• Multiple Database Support:
• BadgerDB (database/drivers/badgerdb/*)
• MySQL (database/drivers/mysql/*)
• Redis (database/drivers/redis/*)
• In-Memory (database/drivers/memory/*)
c. Container Management Layer:
• Container Backends:
• Nomad Integration (internal/container/nomad/*)
• Docker Integration (internal/container/docker/*)
d. Integration Layer:
• VSCode Integration
• Code Server Integration
• Terminal Services
• VNC Support
• Origin-Leaf Architecture (internal/origin_leaf/*)
Relationship Flows
• User → Web Interface/CLI → API Server
• API Server → Database Layer
• API Server → Container Management Layer
• Agent → Container Management Layer
• Proxy → Development Environments
• DNS Services ↔ Development Spaces
Key Design Elements
• Blue rectangles: Core services
• Orange hexagons: Container platforms
• Purple clouds: External integrations
• Yellow diamonds: Security components
Architectural Patterns to Highlight
• Multi-tenant architecture
• Plugin-based database system
• Microservices communication
• Origin-Leaf distribution model
Specific Components
[Client Layer]
• Web UI
• CLI Tools
• VS Code
• Terminal
[Application Layer]
• API Gateway
• Authentication/Authorization
• Template Management
• Space Management
• User/Group Management
• Role-Based Access Control
[Infrastructure Layer]
• Container Orchestration
• Volume Management
• Network Management
• DNS Services
[Storage Layer]
• Database Abstraction
• Multiple Backend Support
Additional Elements
• Security boundaries (showing authentication/authorization flows)
• Resource quotas and limits
• Template flow from definition to deployment
• Monitoring and logging pathways
• API endpoints and integration points