How wwbn/avideo works
Project type and purpose
• This is a full‐stack, modular video streaming platform (AVideo) written in PHP.
• Purpose: allow users to upload, encode, play (on‐demand & live), monetize, and manage video content via a core “Streamer” web app, an “Encoder” service, and a “Live Server.”
• Key domains: user management, video processing, playback, live streaming, plugins/extensions, and background jobs.
File structure
• Top‐level folders:
• admin, feed, objects, plugin, install, updatedb – core web app (MVC‐like PHP + JSON APIs)
• CreatePlugin – CLI/GUI scaffolding for plugin creation
• Dockerfile(s) & docker‐compose – containerized deployment
• deploy – webserver (Apache & Nginx) configs
• node_modules / package.json – client‐side assets & build
• storage – video & auxiliary file storage
• vendor & composer.json – PHP dependencies
• Plugin folder: dozens of self‐contained modules (standalone PHP classes, SQL installers, view templates)
• Background scripts: install/, updatedb/, plugin cron tasks in plugin subfolders
• Live & WebSocket servers: plugin/YPTSocket, plugin/WebRTC, plugin/Live (Nginx RTMP and HLS configs).
README
• Confirms three logical subsystems: Streamer (web UI + API), Encoder (FFmpeg service), Live Server (RTMP/HLS).
• Highlights extensibility via plugins and API, and recommends Docker/Ubuntu for deployment.
Elements
• User‐facing (blue)
• Core services (green)
• Data stores (orange)
• External services (gray)
• Annotations for plugins, cron jobs, and container boundaries.
Detail is key
• Essential services (Encoder, Live, WebSockets).
• How storage (local vs. CDN) and database interact.