Infrastructure & Automation

What I deliver

I automate the operational work that slows your team down: deployment pipelines, environment provisioning, container orchestration, and monitoring. Whether you're moving to Docker, setting up CI/CD, or trying to make your infrastructure reproducible, I can help.

Technologies

Docker and Docker Compose for containerization, GitHub Actions and GitLab CI for pipelines, OpenTofu/Terraform for infrastructure as code, Cloudflare for DNS and tunnels, and Linux administration. I've managed Proxmox clusters, ZFS storage pools, and reverse proxy setups with Traefik and Nginx.

What to expect

Infrastructure that's defined in code, versioned in Git, and deployed automatically. Monitoring and alerting so you know when something breaks before your users do. Documentation that explains the reasoning, not only the steps.

How I approach it

Infrastructure should be something you can rebuild rather than something you are afraid of. A server should be a file in a repository rather than an artefact of whatever somebody did over SSH eighteen months ago. In practice that also means secrets in a real secret store rather than in a repo or an environment file, and backups that are actually restored on a schedule rather than hoped over.

I work across self-hosted and cloud, and I am happy to say when self-hosting is the wrong answer. A lot of what I build ends up on plain Linux machines because it is cheaper and more predictable than the managed equivalent, but not always, and that is a judgement per project rather than a rule.