How yogeshr45/devops-project-two-tier-flask-app works
This repository is a Flask/MySQL message app packaged for deployment through a documented GitHub-to-Jenkins CI/CD workflow on AWS EC2. Users submit messages through the Flask app; it stores them in MySQL and renders stored messages in the page. The graph also preserves the documented pipeline and two-container deployment. Runtime relationships come from app.py; deployment relationships are documented in README.md, since Jenkinsfile and container configuration were not sampled directly.
Main entry points: app.py Flask app · Jenkinsfile Jenkins pipeline · docker-compose.yml Compose services · index.html Message page
Components 9
Web application
- Flask app
app.py - Message page
templates/index.html
CI/CD deployment
- Jenkins pipeline
Jenkinsfile - AWS EC2 host
Container infrastructure
- Compose services
docker-compose.yml - MySQL database
docker-compose.yml
Other components
- Developer
- GitHub repository
- Web visitor
Connections 12
- Developer → GitHub repository: pushes code
README.md - GitHub repository → Jenkins pipeline: triggers build
README.md - Jenkins pipeline → GitHub repository: clones code
README.md - Jenkins pipeline → Compose services: runs deployment
README.md - Jenkins pipeline → AWS EC2 host: deploys on
README.md - Compose services → Flask app: builds service
README.md - Compose services → MySQL database: configures service
README.md - Web visitor → Flask app: requests page
- Flask app → MySQL database: reads messages
app.py - Flask app → MySQL database: writes message
app.py - Flask app → Message page: renders page
app.py - Web visitor → Flask app: submits message