How hyeonsangjeon/youtube-dl-nas works
Main Components
a) Client-Side Components:
• Web Interface (Static Files)
• HTML Templates (static/template/)
• CSS Styles (static/css/)
• JavaScript Logic (static/js/, static/logical_js/)
b) Server-Side Components:
• Web Server (Bottle Framework)
• WebSocket Server (bottle_websocket/)
• Authentication System
• Download Queue Manager
• YouTube-DL Integration (yt-dlp)
c) Storage:
• Download Folder Volume
• Authentication Storage (Auth.json)
Component Relationships
• User authentication flow
• Video download request flow
• WebSocket real-time status updates
• File system interactions
• [Client Tier]
• ↕️ HTTPS/WSS
• [Application Tier]
• ↕️ File I/O
• [Storage Tier]
Component Details
Client Tier:
[Web Browser]
• Login Interface
• Download Queue UI
• WebSocket Client
Application Tier:
[Bottle Web Server (Port 8080)]
• Authentication Module
• Queue Manager
• WebSocket Server
• YouTube-DL Integration
Storage Tier:
[Docker Volume]
• Download Folder
• Auth.json
Additional Elements
• Version information and update scheduler
• Proxy support if enabled
• Supported video quality options
Interactions to Highlight
• Authentication flow
• Download request processing
• Queue management
• Real-time status updates via WebSocket
• File system operations
Key Technical Details to Include:
• Port mapping (8080 default)
• Volume mounting (/downfolder)
• WebSocket connection for real-time updates
• REST API endpoint (/youtube-dl/rest)
• Supported video formats and resolutions
• Daily update scheduler
This system design should clearly show how the application handles both authenticated users and API requests, manages the download queue, and provides real-time status updates through WebSocket connections, all while running within a Docker container with configurable environment variables.