How elmir-ahmed/taskflow_devops works
This repository describes a local DevOps infrastructure lab: Docker provides three target servers, and Ansible configures them over SSH to run application, CI/CD, and monitoring services. The principal workflow is provisioning, inventory-based Ansible configuration, then Compose-managed services. The README also describes a future Git-triggered Jenkins pipeline; it explicitly cautions that this pipeline and effective metrics collection may not yet be configured. No source excerpts were provided, so relationships below rely on README statements only.
Main entry points: docker-compose.yml Target servers · site.yml Deployment playbooks · docker-compose.yml.j2 App Compose template · main.yml App configuration
Components 24
Provisioning
- Target image
Dockerfile.ubuntu - Container bootstrap
entrypoint.sh - Target servers
docker-compose.yml
Ansible control
- Host inventory
ansible/inventory.ini - Deployment playbooks
ansible/playbooks/site.yml - App configuration
ansible/roles/app/tasks/main.yml - CI/CD configuration
ansible/roles/cicd/tasks/main.yml - Monitoring configuration
ansible/roles/monitoring/tasks/main.yml - Common configuration
ansible/roles/common/tasks/main.yml
Application stack
- App Compose template
ansible/roles/app/templates/docker-compose.yml.j2 - Frontend
ansible/roles/app/templates/docker-compose.yml.j2 - Backend API
ansible/roles/app/templates/docker-compose.yml.j2 - MySQL
ansible/roles/app/templates/docker-compose.yml.j2 - phpMyAdmin
ansible/roles/app/templates/docker-compose.yml.j2
CI/CD stack
- CI/CD Compose template
ansible/roles/cicd/templates/docker-compose.yml.j2 - Jenkins
ansible/roles/cicd/templates/docker-compose.yml.j2 - SonarQube
ansible/roles/cicd/templates/docker-compose.yml.j2
Monitoring stack
- Monitoring Compose template
ansible/roles/monitoring/templates/docker-compose.yml.j2 - Prometheus configuration
ansible/roles/monitoring/templates/prometheus.yml.j2 - Prometheus
ansible/roles/monitoring/templates/docker-compose.yml.j2 - Grafana
ansible/roles/monitoring/templates/docker-compose.yml.j2
Other components
- Operator
- Browser user
- Git repository
Connections 31
- Operator → Target image: builds
README.md - Operator → Target servers: starts
README.md - Target image → Target servers: builds
README.md - Container bootstrap → Target servers: starts SSH
README.md - Operator → Deployment playbooks: runs
README.md - Deployment playbooks → Host inventory: uses
README.md - Deployment playbooks → App configuration: applies
README.md - Deployment playbooks → CI/CD configuration: applies
README.md - Deployment playbooks → Monitoring configuration: applies
README.md - App configuration → Target servers: configures via SSH
README.md - CI/CD configuration → Target servers: configures via SSH
README.md - Monitoring configuration → Target servers: configures via SSH
README.md - Common configuration → Target servers: prepares hosts
README.md - App configuration → App Compose template: renders
README.md - CI/CD configuration → CI/CD Compose template: renders
README.md - Monitoring configuration → Monitoring Compose template: renders
README.md - App Compose template → Frontend: starts
README.md - App Compose template → Backend API: starts
README.md - App Compose template → MySQL: starts
README.md - App Compose template → phpMyAdmin: starts
README.md - Frontend → Backend API: calls
README.md - Backend API → MySQL: accesses
README.md - CI/CD Compose template → Jenkins: starts
README.md - CI/CD Compose template → SonarQube: starts
README.md - Monitoring Compose template → Prometheus: starts
README.md - Monitoring Compose template → Grafana: starts
README.md - Prometheus configuration → Prometheus: configures
README.md - Browser user → Frontend: uses
README.md - Git repository → Jenkins: may trigger
README.md - Jenkins → SonarQube: may analyze
README.md - Prometheus → Grafana: visualizes metrics
README.md