How espeon/muse works
Main Components Identification
The system consists of several key services:
• Maki: The core music server (Rust-based)
• Nozomi: The frontend application (Next.js-based)
• Eli: Remote control server
• Umi: Lyrics service (optional component)
• (Future) Honoka: Sōzu control plane
Component Relationships
• HTTP/WebSocket communication between frontend and backend services
• Database connections
• File system access patterns
• Authentication flows
• Media streaming paths
Technical Details to Highlight
• Supported audio formats (MP3, WAV, FLAC, AIFF)
• Database migrations
• API middleware (HMAC, JWT)
• File metadata extraction
• Frontend state management (stores/)
• Docker containerization
Create clear boundaries between:
• User Interface Layer
• Application Services
• Data Storage
• External Services
• Infrastructure Components
Additional Elements
Annotations for:
• Scaling points
• Security boundaries
• Optional components
• Future expansion points (recommendation engine, analytics)
Remember to indicate the containerized nature of the deployment and how the services interact within the Docker network. Also, highlight the optional nature of some components (like Umi) and how the system gracefully handles their absence.
This architecture should emphasize the system's ability to handle large music collections efficiently while maintaining low resource usage, as mentioned in the key features.