How beclab/olares works
High-Level Architecture Components
a) User Interface Layer
• Desktop Application (apps/desktop)
• Web-based Management Console (third-party/ks-console)
• Client Applications (mentioned in README for Android, iOS, Windows, Mac, Chrome Plugin)
b) Application Layer
• Built-in Apps (files, vault, market, notifications, etc.)
• Third-party Apps
• AI Applications and Models
c) Framework Layer
• App Service (frameworks/app-service)
• System Server (frameworks/system-server)
• Backend For Launcher (frameworks/bfl)
• GPU Management (frameworks/GPU)
• TAPR (Application Runtime)
d) Infrastructure Layer
• Kubernetes/K3s Base
• Storage Systems (JuiceFS, MinIO)
• Database Services
• Authentication (Authelia)
• Network Management (Headscale, Tailscale)
Key Relationships to Highlight
a) Data Flow
• Client requests → BFL Proxy → Application Services
• Storage requests → JuiceFS/MinIO
• Authentication flow → Authelia → Apps
b) Control Flow
• System Server → App Service → Applications
• GPU Manager → AI Applications
• Backup Server → Storage Systems
Component Grouping
• Security Group (Authelia, Headscale, etc.)
• Storage Group (JuiceFS, MinIO, Backup)
• Runtime Group (TAPR, App Service)
• AI Services Group (GPU management, AI models)