How chuot/rdio-scanner works
Main Components Identification
a) Frontend (Client)
• Angular-based web application
• Progressive Web App (PWA) capabilities
• Native mobile apps (iOS/Android)
b) Backend (Server)
• Go-based server application
• API endpoints
• WebSocket connections for live feed
c) External Systems
• Various radio recorder integrations
• File system watchers
• Database storage
[Client Layer]
• Web Application (Angular)
• Mobile Apps (iOS/Android)
• ↕ (HTTP/WebSocket)
[Server Layer]
• API Gateway
• Authentication/Authorization
• Core Services
• ↕
[Integration Layer]
• Directory Watchers
• API Connectors
• File Processors
• ↕
[Storage Layer]
• Database
• File Storage
Component Details
Frontend Components (Blue):
• Admin interface
• Search functionality
• Live feed components
• Mobile apps as parallel clients
Backend Services (Green):
• API endpoints (/api)
• WebSocket handlers
• Authentication service
• File processing service
• Configuration management
• Downstream distribution
Integration Points (Orange):
• Directory watch service
• API connectors for different recorders
• FFmpeg processing
• File system interactions
Storage (Purple):
• Database connections
• Audio file storage
• Configuration storage
Data Flow Indicators
• Client-server communication (HTTP/WebSocket)
• Audio file ingestion paths
• Live streaming paths
• Configuration management flows
• Authentication flows
Additional Elements
Notes for:
• Scalability points
• Security boundaries
• Configuration options
• Deployment considerations
• Docker container boundaries
Remember to highlight the system's unique features:
• Real-time audio streaming
• Multiple recorder support
• Administrative capabilities
• Mobile app integration
• Access control and security