Infrastructure · CI/CD · Prometheus
A portfolio that monitors itself
CI/CD, a hardened non-root container, a health endpoint and its own metrics — DevOps practice, shipped.
At a glance
CI/CD
lint → build → push
non-root
hardened container
/metrics
Prometheus endpoint
A separate project from this site. The code is in a private GitHub repository; I can walk you through it on a call.
The problem
Every DevOps CV lists pipelines, containers and observability. Claims are cheap — the portfolio itself should be the proof, not another static brochure.
How it is built
- GitHub Actions: lint, typecheck and build, then push the image to GHCR
- Multi-stage Dockerfile with a non-root runtime and a health check
- Standalone Next.js with a JSON /healthz endpoint
- Prometheus metrics exported by the app itself
Where it stands
The repository doubles as a reference architecture for containerised web apps. The footer links each deployment to its commit, and the app reports its own health and metrics.
- A reference architecture for containerised apps
- Every deployment traceable to its commit
- Prometheus metrics out of the box