How blackcandy-org/blackcandy works
Main Components Identification
a. Frontend Layer:
• Web Interface (Rails views + JavaScript/Stimulus controllers)
• Mobile Apps (iOS and Android clients)
• PWA Support (manifest.json and service-worker.js)
b. Backend Layer:
• Rails Application Server
• API Controllers (v1 API endpoints)
• Authentication System
• Media Processing Services
• Stream Controllers
c. Storage Layer:
• Database (SQLite/PostgreSQL)
• File Storage (Media files)
• Active Storage (for images)
d. External Services:
• Discogs API Integration
• Nginx (optional for file serving)
[Mobile Apps/Web Clients] → [Load Balancer/Nginx]
• ↓
[Rails Application Server] → [API Controllers]
• ↓
[Core Services]
• Media Processing
• Authentication
• Playlist Management
• Search Service
• ↓
[Storage Layer]
• Database
• File Storage
• ↓
[External Services]
• Discogs API
Key Flows
• User authentication flow
• Media streaming path
• File synchronization process
• Search and filtering operations
• Playlist management
• Cover art retrieval from Discogs
Technical Details
Annotations for:
• Port mappings (3000)
• Supported audio formats
• Database adapters
• Storage mount points
• API endpoints structure
• Media processing capabilities
Notes Section
Important notes about:
• Scalability options
• Security considerations
• Configuration requirements
• Mobile app integration points
Remember to emphasize the modular nature of the system, showing how components like media processing, authentication, and streaming can be configured or swapped based on deployment needs.