How boostcampwm-2024/web20-camon works
Project type and purpose
• This is a full‑stack, microservice‑oriented web application (“Cam’On”) for real‑time video broadcasting, chat, recording, attendance tracking, and archival management.
• The README confirms core features: real‑time streaming (WebRTC/Mediasoup), chat (WebSockets), record/encoding (FFmpeg), attendance (NestJS + MySQL), and a React/Tailwind front end.
File structure
• Top‑level “apps” folder houses five services:
• api: REST API (NestJS) for auth, attendance, bookmarks, broadcast metadata, record metadata, member profiles.
• chat: WebSocket (NestJS Gateway) handling real‑time chat, using in‑memory + Redis.
• media: Mediasoup SFU service (NestJS) for routing video/audio, transport & consumer/producer management.
• record: Node.js service handling media ingest, FFmpeg-based conversion & queuing, object‑storage integration.
• client: React + Vite front end for UI, authentication, video publish/view, chat, attendance, archive.
• Root docker-compose.yml & per‑service Dockerfiles + GitHub Actions workflows indicate containerized deployment.
• Shared infra concerns: MySQL, Redis, Nginx (ingress), object storage (S3‑compatible), CI/CD.
README for additional insights
• Tech stack: TypeScript, pnpm, React/Tailwind, NestJS, MySQL, FFmpeg, Docker, GitHub Actions, NCloud.
Detailed breakdown of essential elements
• Edge router: “Nginx / LB” directing HTTP→Client/API, WS→Chat/Media.
• Infrastructure layer: MySQL, Redis, S3 Storage
• Bottom: “GitHub Actions” → builds Docker images → pushes to registry → triggers container deployment.
Summary