Feature and its Use Cases

What is the feature?

This feature proposes implementing a complete Docker-based full stack setup for EduAid, including:

• Containerized Python backend (Flask API)
• Containerized React web frontend
• Docker Compose orchestration
• Environment variable management using .env
• Separate development and production configurations

The goal is to allow contributors to run the entire application stack using a single command.

How would users benefit from it?

• Simplified onboarding for new contributors
• Eliminates dependency and version conflicts
• Standardized development environment
• One-command startup (docker-compose up --build)
• Easier CI/CD integration
• Deployment-ready infrastructure
• Improved maintainability and scalability

What scenarios would this feature address?

• New contributors cloning the repository
• Avoiding manual installation of Python/Node dependencies
• Cross-platform consistency (Windows/macOS/Linux)
• Preparing the project for cloud deployment
• Reducing "it works on my machine" issues
• Running backend and frontend services in a unified environment

Additional Context

This feature will introduce the following files and configurations:

• backend/Dockerfile
• eduaid_web/Dockerfile
• backend/.dockerignore
• eduaid_web/.dockerignore
• docker-compose.yml
• Optional: docker-compose.prod.yml
• .env.example
• README documentation updates

Expected Usage After Implementation

docker-compose up --build

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates