I'm Arslan Asad Qazi, and I build the pipelines that get code from a commit to production without breaking or leaking anything along the way.

Arslan is a final-year Computer Science student at FAST-NUCES Karachi, graduating in June 2027. His focus is DevOps, Cloud, and DevSecOps engineering, the practical side of getting software built, tested, secured, and deployed without someone babysitting every step.

He has hands-on experience across CI/CD pipelines, containerization, cloud infrastructure, and security tooling, mostly gained by building real projects. This portfolio is one of those projects. It's deployed the same way he'd deploy anything else.

This site runs through an actual deployment pipeline rather than a static export pushed to a CDN. Every push to main works through tests, a Docker build, a Trivy vulnerability scan, and a push to GHCR before a deploy is even attempted.

The container image is built once and tagged with the commit SHA, then pushed to GitHub Container Registry, which sits next to the code and reuses GitHub auth instead of a separate registry account. An Ansible playbook handles the actual deploy: it runs on every push, SSHes into a single Oracle Cloud VM, pulls the new image, and recreates the container.

Caddy sits in front of the container as a reverse proxy and handles HTTPS automatically for arslanasadqazi.is-a.dev, with no separate Certbot cron job to maintain. There's no Terraform here either, because provisioning a single VM by hand in the Oracle console is simpler than writing infrastructure as code for one resource. That trade-off flips once there's more than one thing to provision.

The full reasoning behind each of these choices is written up as ADRs in docs/adr/ in the repo.