How iam-veeramalla/mern-docker-compose works
Project type and purpose
• This is a full-stack MERN (MongoDB, Express, React, Node.js) application packaged and orchestrated via Docker.
• Purpose: a simple records-management UI (React/Vite/Tailwind) communicating with an Express/Node REST API, which in turn reads/writes to MongoDB.
File structure
• Top level:
• docker-compose.yaml – defines a three-container setup (frontend, backend, mongodb) on a Docker network named “demo.”
• mern/frontend – React app scaffolded with Vite, styled with Tailwind, plus Cypress end-to-end tests.
• mern/backend – Express server with routes/record.js, MongoDB connection code (db/connection.js), and its own Dockerfile.
• Notice MVC-style breakdown in backend (server.js loads routes; routes call DB connection).
• Frontend includes component folder (Navbar, Record, RecordList), assets, index.html, and Vite config.
README for additional insights
• Describes a three-container workflow: build and run frontend & backend images, and a standard MongoDB image.
• Ports: frontend on 5173, backend on 5050, MongoDB on 27017.
• Uses a dedicated Docker network so containers can refer to each other by name.
• Offers an alternative “docker compose up -d” command to launch all services together.
Elements
• “HTTP GET/POST” from Browser → Frontend
• “REST API” from Frontend → Backend
• “MongoDB Driver” from Backend → MongoDB
• (Optional) “Cypress E2E Tests” from Test Runner → Frontend