Lagos, Nigeria | LinkedIn | Blog | Email: adelekedare2012@gmail.com
I work on the practical side of backend and infrastructure: getting services deployed, watched, recovered, and documented well enough that another engineer can understand what is going on.
Right now my strongest work sits around CI/CD, Docker, AWS EC2 deployments, monitoring, and small backend systems that show reliability thinking.
| Area | Work You Can Review |
|---|---|
| CI/CD and release automation | github-actions-ec2-pipeline - Node 22/24 build and test checks, controlled EC2 deployment flow, PM2 reloads, rollback script, and scheduled health-check workflow |
| Backend reliability | api-reliability-suite - FastAPI service with auth, rate limiting, readiness checks, metrics, tracing, dashboards, and fallback behavior |
| Container pipeline checks | github-actions-cicd-demo - GitHub Actions matrix tests, ESLint, Trivy SARIF upload, Docker Buildx, and GHCR publishing |
| IT systems operations | glpi-ticketing-system - Docker Compose GLPI helpdesk lab with MariaDB, persistent storage, operations scripts, and ITSM workflow notes |
| DevOps lab work | devops-labs - hands-on labs across Linux, AWS, Docker, Kubernetes, Terraform, Ansible, Prometheus, and Grafana |
| Project | Why It Is Here | Evidence |
|---|---|---|
| API Reliability Suite | A backend reliability project: JWT auth, refresh-token rotation, rate limits, readiness checks, structured logs, Prometheus metrics, Grafana dashboards, Jaeger tracing, and Redis-backed fallback behavior | Passing CI, Security, and Docs runs, plus Grafana and AI-debug screenshots |
| EC2 Release Pipeline | A GitHub Actions release flow for a Node/Express app on EC2. It tests on Node 22/24, deploys from a manual run or v* tag, reloads with PM2, and keeps rollback logic in scripts/deploy.sh |
Passing CI matrix run, successful tagged deploy run, Release v1.0.20, and historical EC2 screenshots in devops-labs |
| Container CI/CD Pipeline | A container pipeline lab with tests, linting, Trivy SARIF, Docker Buildx, GHCR publishing, and simulated staging/production rollout steps | Passing GitHub Actions workflow. The deploy stage is intentionally marked as simulated until a real target is connected |
| GLPI Helpdesk Lab | A self-hosted ITSM/helpdesk lab using GLPI, MariaDB, Docker Compose, named volumes, internal database networking, ticket categories, SLA notes, and support roles | Compose file, operations runbook, backup/restore/smoke-test scripts, dashboard screenshot, sample ticket, asset inventory, smoke note, and a setup write-up |
| DevOps Labs | My broader lab archive. It is useful because it shows the path from Linux and AWS basics into Terraform, Ansible, Kubernetes, and monitoring work | The root README points to the strongest capstones; the companion repo map lives in docs/evidence-map.md |
devops-labs is the umbrella: it keeps the notes, screenshots, scripts, and learning path together. When a lab became strong enough to stand on its own, I keep it as a separate repo and make that repo easier to review first.
That is why the polished standalone repos above are the front door. The older capstone app repos still matter, but they are companion evidence, not the headline, until their CI, screenshots, and READMEs are cleaned up.
| Skill Area | Projects |
|---|---|
| GitHub Actions and release automation | github-actions-ec2-pipeline, github-actions-cicd-demo |
| AWS, EC2, IAM, and deployment operations | github-actions-ec2-pipeline, devops-labs |
| Docker and service deployment | glpi-ticketing-system, github-actions-cicd-demo, api-reliability-suite |
| Monitoring and observability | api-reliability-suite, devops-labs |
| Linux and systems administration | devops-labs, glpi-ticketing-system |
| Backend infrastructure | api-reliability-suite, github-actions-ec2-pipeline |
I try to keep the portfolio honest. Labs are called labs. Simulated deployments are called simulated. When a project is strong, I want the proof to be close by: a workflow run, a screenshot, a log, a dashboard, a test report, or a short note explaining what was verified.
- GLPI helpdesk implementation - my write-up on setting up GLPI, troubleshooting the web server, and organizing tickets, roles, assets, SLA notes, and reports.
- dev.to/darestack - notes from my DevOps, Linux, backend reliability, and infrastructure work.