How epoupon/lms works
Main Components
A. Frontend Layer:
• Web Interface (Wt-based UI components in src/lms/ui/)
• Media Player Component
• Explore/Browse Interface
• Admin Interface
• Authentication UI
B. Backend Services Layer:
• Authentication Service (src/libs/services/auth/)
• Artwork Service (src/libs/services/artwork/)
• Scanner Service (src/libs/services/scanner/)
• Recommendation Service (src/libs/services/recommendation/)
• Scrobbling Service (src/libs/services/scrobbling/)
• Feedback Service (src/libs/services/feedback/)
C. Core Components:
• Database Layer (src/libs/database/)
• Metadata Processing (src/libs/metadata/)
• Audio Processing (src/libs/av/)
• Image Processing (src/libs/image/)
• Core Utilities (src/libs/core/)
D. External Integrations:
• ListenBrainz Integration
• Subsonic/OpenSubsonic API
• Authentication Backends (PAM, Internal)
Relationships
• User requests flow from Frontend → Backend Services
• Service dependencies between components
• Data flow between services and core components
• External service integration points
Design Elements
[Frontend Layer]
• ↑↓
[API Layer (Subsonic/REST)]
• ↑↓
[Service Layer]
• ↑↓
[Core Components]
• ↑↓
[Storage Layer]
Important Details
A. Data Flow:
• Music file processing pipeline
• Authentication flow
• Recommendation engine process
• Scrobbling/feedback synchronization
B. Storage:
• Music file storage
• Database storage
• Cache storage (artwork, transcoding)
C. Security Boundaries:
• Authentication checkpoints
• User permission boundaries
• API security layers
Specific Implementation Notes
• Wt framework integration
• Modular service architecture
• Multiple authentication backend options
• Media processing pipeline
• Recommendation engine components