How washington-kibichii/youtube-clone-mern works
Project type and purpose
• This is a full-stack MERN (MongoDB, Express, React, Node.js) YouTube clone.
• Purpose: allow users to register/login (JWT), upload/view videos (stored in Firebase Storage), interact via likes/comments, manage channels/playlists, and use a “Studio” interface for content management.
File structure
• Top-level:
• docker-compose.yml – orchestrates services in Docker
• frontend/ – React single-page app
• backend/ – Node/Express API server with Handlebars views for password/reset flows
• backend/ breakdown:
• Database/ (database.js) – MongoDB connection setup
• Models/ – Mongoose schemas (user, videos, trending)
• Router/ – Express route modules (auth, videos, comments, likes, channel, studio)
• public/ & views/ – static assets & HBS templates for emails/reset pages
• server.js, Dockerfile, vercel.json – entrypoint, deployment config
• frontend/ breakdown:
• src/ – React code (App.jsx, Components/, Firebase.js, main.jsx, CSS, assets)
• public/, index.html, netlify.toml, Dockerfile, vite.config.js – bundling, hosting, deployment
README insights
• Deployment: Frontend on Netlify (netlify.toml), backend on Vercel (vercel.json) or via Docker Compose
• Features: auth flows, video CRUD, playlists, studio, responsive UI
a. Main components
• React Frontend (SPA hosted on Netlify or Docker)
• Node/Express Backend API (with Handlebars views for email flows)
• MongoDB (Atlas or local via Docker)
• Firebase Storage (video/file storage)
• External Email Service (via Nodemailer using GMail SMTP)
• Docker Compose (local orchestration) or cloud hosts (Netlify, Vercel)
b. Relationships & interactions
1. User’s browser ⇄ React Frontend (HTTP/WS)
2. Frontend → Backend API (REST calls with Bearer JWT)
3. Backend → MongoDB (Mongoose queries)
4. Backend → Firebase Storage (upload/download via SDK)
5. Backend → Email Service (password reset emails)
6. Docker Compose connects Frontend, Backend, MongoDB in local dev
c. Architectural patterns & principles
• Client-Server separation (React SPA vs. REST API)
• MVC on backend: Router (controllers) → Models → Database
• Stateless JWT authentication
• Externalize large-object storage (Firebase) rather than DB blobs
• Deploy via containers or serverless platforms
d. Key technologies/frameworks
• React + Vite (frontend bundler)
• Express.js + Node.js (backend)
• Mongoose + MongoDB Atlas or local Docker container
• Firebase Storage SDK
• JSON Web Tokens for auth
• Docker & docker-compose for local orchestration
• Netlify (frontend), Vercel (backend) as deployment targets
Detail
• Mongoose Models interacting in the backend layer
• That JWT tokens travel in HTTP headers between FE and BE