How fomainspi/two-tier-devops-app works
This repository demonstrates a two-tier web app and its documented delivery workflow. A browser loads the React interface, which requests a message from the Express API and displays the response. Separately, the README describes a developer-to-GitHub-to-Jenkins workflow that builds Docker images and deploys the frontend and backend with Docker Compose. The application call path is visible in the sampled source; deployment links reflect README statements because the deployment files were not sampled.
Main entry points: Jenkinsfile Jenkins Pipeline · docker-compose.yml Compose Deployment · App.js Message UI · index.js React Entry
Components 10
Application
- React Entry
frontend/src/index.js - Message UI
frontend/src/App.js - Express API
backend/server.js
Delivery Workflow
- GitHub Repository
- Jenkins Pipeline
Jenkinsfile - Frontend Image
frontend/Dockerfile - Backend Image
backend/Dockerfile - Compose Deployment
docker-compose.yml
Other components
- User Browser
- Developer
Connections 11
- User Browser → React Entry: loads app
README.md - React Entry → Message UI: renders
frontend/src/index.js - Message UI → Express API: requests message
frontend/src/App.js - Express API → Message UI: returns JSON
backend/server.js - Developer → GitHub Repository: pushes code
README.md - GitHub Repository → Jenkins Pipeline: triggers pipeline
README.md - Jenkins Pipeline → Frontend Image: builds image
README.md - Jenkins Pipeline → Backend Image: builds image
README.md - Jenkins Pipeline → Compose Deployment: deploys services
README.md - Compose Deployment → Frontend Image: runs service
README.md - Compose Deployment → Backend Image: runs service
README.md