How claceio/clace works
Main Components
a. Core Server Components:
• HTTP/HTTPS Server (ports 25222/25223)
• Authentication System (OAuth/SSO)
• Router & Request Handler
• App Manager
• Container Manager
• Plugin System
• Metadata Store (SQLite)
b. Application Components:
• App Runtime Environment
• Static File Server
• Template Engine
• Security Sandbox
• Virtual Filesystem
• Store System (SQLite-based)
c. Development Tools:
• TailwindCSS Integration
• DaisyUI Integration
• esbuild Module Generator
• Development Mode Handler
Component Relationships
• External requests → HTTP Server → Router → App Handler → App Runtime
• App Runtime ↔ Plugin System
• App Runtime ↔ Container Manager (for containerized apps)
• App Runtime ↔ Virtual Filesystem ↔ SQLite Storage
• Development Tools → Static Assets → Virtual Filesystem
Specific Implementation Details
[External Clients] → [HTTPS Server (25223)]
• [HTTP Server (25222)]
• ↓
[Authentication Layer (OAuth/SSO)] → [Router]
• ↓
• [App Manager & Handler]
• ↓
• ┌─────────┴──────────────┐
• ↓ ↓
• [App Runtime Environment] [Container Manager]
• ↓ ↓
• [Plugin System] [Docker/Podman]
• ↓
• ┌─────┴────┬────────┐
• [Store API] [Templates] [Static Files]
• ↓ ↓ ↓
[SQLite DB] [HTML/CSS] [Virtual FS]
Key Architectural Patterns to Highlight
• Plugin-based Architecture: Show how the plugin system enables extensibility
• Security Model: Illustrate the sandboxed execution environment
• GitOps Workflow: Show the deployment flow from Git repositories
• Virtual Filesystem: Demonstrate content-hash based file serving
• Container Integration: Show how containerized apps are managed
Important Notes
• Version numbers for major components
• Security boundaries clearly
• Async vs sync operations
• Optional components (like container support)
• Configuration paths
• Monitoring/logging points
Technical Details
• Go-based implementation
• SQLite as the current storage backend
• Support for both HTTP and HTTPS
• Integration with external services (Docker/Podman)
• Authentication providers
• Static file optimization (Brotli compression)
This architecture reflects Clace's nature as a sophisticated web application platform that can handle both traditional and containerized applications while maintaining security and performance.