Problem Statement
The repository currently lacks a standardized local development environment and does not have a live production deployment:
- No Containerization: Contributors must manually manage local Node.js environments and dependencies, leading to potential "it works on my machine" errors during GSSoC.
- No Live Preview: There is no live URL or deployment setup for the project, making it difficult for maintainers and contributors to instantly preview UI changes or read the documentation online.
Proposed Solution
Introduce Docker and Docker Compose configurations to provide an isolated, one-command local development setup.
Configure and connect the project for live deployment on Vercel or Render so that a live link can be permanently displayed in the README.md.
Key Deliverables
- A root-level Dockerfile optimized for Next.js development.
- A docker-compose.yml file mapping port 3000 with local volume mounting for real-time hot-reloading.
- A .dockerignore file to exclude node_modules and .next folders from the build context.
- A live deployment configuration.
- An updated README.md containing the deployment link and clear instructions on how to run the project using Docker.
Benefits
- Frictionless Onboarding: New contributors can spin up the project with a single command without worrying about their local Node.js version.
- Visibility: Gives the project a public-facing URL where students can actually read the structured CSE notes without needing to clone the code.
Problem Statement
The repository currently lacks a standardized local development environment and does not have a live production deployment:
Proposed Solution
Introduce Docker and Docker Compose configurations to provide an isolated, one-command local development setup.
Configure and connect the project for live deployment on Vercel or Render so that a live link can be permanently displayed in the README.md.
Key Deliverables
Benefits