How mkg789/devops_proj1 works
This repository packages and deploys the ElectronicsWeb application rather than containing its application code. Its documented workflow builds frontend and backend container images, publishes them to GHCR, transfers them to Harbor, and deploys the services to Kubernetes; user requests then flow through the frontend’s Nginx proxy to the backend and MongoDB Atlas. Docker, Kubernetes, and Helm configuration are represented. Relationships are based on the README because no source excerpts were provided; Helm and Argo CD are described as planned, so no Argo CD runtime component is shown.
Main entry points: backend-service.yaml Backend Service · frontend-service.yaml Frontend Service · build-images.yml GitHub Actions Workflow · nginx.conf Nginx Proxy
Components 18
Image Delivery
- GitHub Actions Workflow
.github/workflows/build-images.yml - Docker Image Builds
- GHCR
- Harbor Registry
Container Configuration
- Backend Dockerfile
docker/backend/Dockerfile - Frontend Dockerfile
docker/frontend/Dockerfile - Nginx Proxy
docker/frontend/nginx.conf
Kubernetes Deployment
- Helm Chart
helm/electronicsweb - Backend Deployment
kubernetes/backend-deployment.yaml - Backend Service
kubernetes/backend-service.yaml - Frontend Deployment
kubernetes/frontend-deployment.yaml - Frontend Service
kubernetes/frontend-service.yaml
Application Runtime
- React Frontend
- Node.js / Express Backend
Other components
- Developer
- Application Repositories
- Browser User
- MongoDB Atlas
Connections 17
- Developer → Application Repositories: pushes changes
README.md - Application Repositories → GitHub Actions Workflow: triggers build
README.md - GitHub Actions Workflow → Docker Image Builds: builds images
README.md - Backend Dockerfile → Docker Image Builds: configures backend
README.md - Frontend Dockerfile → Docker Image Builds: configures frontend
README.md - Docker Image Builds → GHCR: publishes images
README.md - GHCR → Harbor Registry: manual transfer
README.md - Harbor Registry → Backend Deployment: provides images
README.md - Harbor Registry → Frontend Deployment: provides images
README.md - Backend Deployment → Backend Service: exposes backend
README.md - Frontend Deployment → Frontend Service: exposes frontend
README.md - Browser User → Frontend Service: accesses
README.md - Frontend Service → React Frontend: routes requests
README.md - React Frontend → Nginx Proxy: serves through
README.md - Nginx Proxy → Backend Service: proxies API requests
README.md - Backend Service → Node.js / Express Backend: routes requests
README.md - Node.js / Express Backend → MongoDB Atlas: communicates with
README.md