How dashotv/tower works
Main Components
a. Core Services Layer:
• Media Management Service (internal/app)
• Plex Integration Service (internal/plex)
• Import Service (internal/importer)
• Fanart Service (internal/fanart)
b. Worker System:
• Downloads Workers
• File Management Workers
• Plex Sync Workers
• Media Update Workers
• Index Management Workers
c. External Integrations:
• TMDB Client
• TVDB Client
• Plex Media Server
• NZBGet Integration
• Runic Integration
• Seer Integration
• Flame Integration
d. Data Storage:
• MongoDB (evident from models and database operations)
• File System Storage
Relationship Flows
• API Routes → Core Services
• Core Services ↔ Worker System
• Core Services ↔ External Integrations
• Workers → Data Storage
• Plex Integration ↔ Plex Media Server
Specific Implementation Details
• Blue rectangles: Core services
• Green rectangles: Workers
• Purple diamonds: External integrations
• Yellow rectangles: API routes
Key Architectural Patterns to Highlight
a. Event-Driven Architecture:
• Event flow between components (.golem/events/)
• Worker queue system
b. Modular Design:
• Separate internal packages
• Clear separation of concerns
Component Details
• Media management flows (movies, series, episodes)
• Download processing pipeline
• Plex synchronization mechanism
• File management system
Technical Stack Indicators
Technology labels:
• Go (main implementation language)
• MongoDB
• Plex API
• External APIs (TMDB, TVDB)
Additional Elements
Annotations for:
• Configuration management (.golem/config.yaml)
• API endpoints (.golem/routes/)
• Worker definitions (.golem/workers/)
• Model definitions (.golem/models/)