How ranyaserraj/devops_projet works
Project type and purpose
• This is a full-stack, containerized ERP/CRM application (“IDURAR ERP CRM”) composed of a React-Vite frontend, a Node.js/Express backend, and a MongoDB database.
• It also includes a CI/CD pipeline using Jenkins and a monitoring stack built on Prometheus, Grafana, Alertmanager, cAdvisor, and Node Exporter.
File structure
• Top-level folders:
• frontend/ – React app code, public assets, Vite config, Dockerfile
• backend/ – Node.js API, controllers, models, middleware, Dockerfile
• monitoring/ – Prometheus & Grafana configs, dashboards, exporters
• jenkins/ – Jenkins pipeline definitions, Docker Compose for CI/CD
• tests/ – automated tests for backend, frontend, integration, performance
• docker-compose.yml & docker.env – orchestrates all core services
• Presence of separate Dockerfiles and docker-compose.yml indicates container-based deployment.
• Jenkinsfile and monitoring folder show additional infrastructure components beyond the core app.
README for additional insights
• Architecture section describes three core services (frontend:3000, backend:5000, mongo:27017) plus a monitoring layer (Prometheus:9090, Grafana:3001).
• CI/CD is managed by Jenkins in its own container.
Elements
• Clear, textual labels for each container/service (e.g., “React Frontend (3000)”, “Express API (5000)”, “MongoDB (27017)”).
• Blue rectangles for application components (frontend, backend)
• Orange or yellow parallelograms for CI/CD and monitoring services