How erikmeliska/meteleskublesku works
Main Components
a. Client Layer:
• Next.js Frontend Application
• Client-side Routes (/movie/[...params], index)
b. API Layer:
• Next.js API Routes
• Media Endpoints (getAudio, getImage, getMovie)
• YouTube Integration (searchYoutube)
• Management (getMovieList)
• Audio Processing (extractAudio)
c. External Services:
• Original Server (legacy system)
• YouTube API
• Cache Storage System
[Client Layer]
• ↕
[API Layer]
• ↕
[External Services]
Key Relationships to Highlight
a. Data Flow:
• Client requests → API Routes
• API Routes → Cache check
• Cache miss → External services
• Cache hit → Direct media serving
• Media storage flow
b. Caching Strategy:
• How the application serves as a caching proxy
• Cache check/store workflow
Specific Implementation Details
• Next.js Application Container
• Pages (index.js, movie/[...params].js)
• API Routes (all files under /api)
• Cache Storage
• Image cache
• Audio cache
• Movie cache
• External Systems
• Original meteleskublesku.cz server
• YouTube API integration
Important Notes
a. Emphasize:
• The caching mechanism as it's a key feature
• API route organization
• External service interactions
b. Include:
• Docker container boundary (based on Dockerfile presence)
• Environment configuration points
• Cache storage location