Content Broadcasting Backend Project | Interview Assignment Project |

A backend system for educational content distribution — teachers upload subject content, principals approve it, and students access live content via public APIs. ## 🛠 Tech Stack - **Runtime**: Node.js - **Framework**: Express.js - **Database**: MySQL - **Auth**: JWT + bcrypt - **File Upload**: Multer (local storage by default, S3 if configured) / cloudinary storage - **Rate Limiting**: express-rate-limit ## 📁 Project Structure ``` src/ ├── app.js # Entry point ├── config/ │ ├── db.js # PostgreSQL pool │ └── storage.js # S3 or local multer config ├── controllers/ │ ├── auth.controller.js # Register, login │ ├── content.controller.js # Upload, approve, reject │ └── broadcast.controller.js # Public live content ├── middlewares/ │ ├── auth.middleware.js # JWT + RBAC │ └── error.middleware.js # Error handler ├── routes/ │ ├── auth.routes.js │ ├── content.routes.js │ └── broadcast.routes.js ├── services/ │ └── scheduling.service.js # Rotation algorithm └── utils/ ├── migrate.js # DB table creation └── seed.js # Demo data ``` ## 📝 Assumptions - `start_time` and `end_time` must both be provided (or neither) — content without a time window is never shown - Times are stored and compared in UTC - The rotation clock resets daily at midnight UTC for simplicity - Content can only go from `pending` → `approved` or `pending` → `rejected` (no re-approval) - Subjects are stored in lowercase for consistent matching