How moontechlab/lunatv works
Project type and purpose
• MoonTV is a full-stack, server-rendered web application (Next.js 14 + App Router) that aggregates multiple video sources into a unified player/UI, provides a built-in admin panel (REST API under /src/app/api/admin/*), and persists user data (favorites, watch history) in Redis-style stores (Kvrocks/Redis/Upstash). It’s packaged as a Docker-ready monolith with PWA support.
File structure
• Top-level Docker + CI/CD: Dockerfile, .dockerignore, GitHub Actions workflow under .github/workflows/docker-image.yml
• Config & build: next.config.js, tsconfig.json, tailwind.config.ts, jest.config.js, lint/prettier configs
• App Router pages & API routes:
• /src/app/*.tsx (UI pages: home, search, detail, play, admin)
• /src/app/api/*/**/route.ts (REST endpoints for admin, auth, search, proxy, live, douban, etc.)
• Components: /src/components (reusable React components)
• Hooks: /src/hooks (e.g., useLongPress)
• Lib: /src/lib (db clients, auth, external-API wrappers, caching, utils)
• Middleware: src/middleware.ts (edge middleware for auth/redirects)
README for additional insights
• Tech stack: Next.js 14, Tailwind CSS, TypeScript, ArtPlayer, HLS.js
• Storage options: Kvrocks, Redis, Upstash (via env vars NEXT_PUBLIC_STORAGE_TYPE, KVROCKS_URL, REDIS_URL, UPSTASH_URL/TOKEN)
• Deployment: Docker Compose (core + Kvrocks/Redis), Zeabur one-click
a. Main components:
• Client (Browser/PWA)
• Next.js Server (Node.js container)
• Data stores (Kvrocks/Redis/Upstash)
• External APIs & services (Douban API or proxies, video/CDN endpoints)
b. Relationships & data flows:
1. Client → HTTP(S) → Next.js Server
‑ UI page requests (SSR/SSG) and API calls (/api/*)
2. Next.js Server ↔ Data store
‑ Reads/writes favorites, watch history, config cache
3. Next.js Server → External services
‑ Douban data fetch, site-provided VOD APIs, ad-skipping logic, image proxies, HLS segment proxy
4. Client ← HLS.js/ArtPlayer ← (via Next.js proxy or direct CDN) video streams
c. Architectural patterns / design principles:
• Monolithic Node.js container with layered structure: Presentation (React+Tailwind), Business Logic (API routes + lib services), Data Access (db clients), Integration adapters (external API wrappers)
• API routes as serverless-style functions inside Next.js
• PWA caching (service worker) for offline/installation
• Edge middleware for auth and routing
• Config driven by environment variables injected at container runtime
d. Key technologies/frameworks:
• Next.js 14 App Router & Server Actions
• React + Tailwind CSS
• Docker (core + Kvrocks/Redis containers)
• Redis-compatible stores (Kvrocks, Upstash)
• ArtPlayer & HLS.js for video playback
• Jest + ESLint + Prettier for code quality
Elements
• Clear labels on each component (e.g., “Next.js App Container”, “Kvrocks Store”, “Douban Proxy API”)
• Blue rectangles for UI/client
• Green for application/server
• Purple clouds for external services/CDN