Projects

Projects & selected work

Most of the work I can show publicly lives in my Talos Kubernetes homelab. This page also includes a few examples from my professional experience, kept high-level where the underlying systems are private.

Selected professional work

Cloud platforms & delivery

Professional examples are kept high-level because the underlying systems and customer environments are private.

01

Cloud platform engineering

TrueFullstaq

At TrueFullstaq, I worked on Azure environments delivered and maintained with Terraform. My work included private networking, managed identities, Key Vault integration, monitoring, troubleshooting and documenting practical follow-up actions.

What I worked on

  • Building and adapting reusable Terraform configuration for Azure environments.
  • Investigating application and Kubernetes connectivity problems, including virtual-network integration and outbound connectivity.
  • Using monitoring and diagnostic data to trace failures and explain the available technical options.

I wanted each investigation to end with a concrete next step. Depending on the cause, that could mean adjusting monitoring, changing part of the network architecture or improving the Terraform configuration used for later environments. I also walked customers and colleagues through the evidence behind the recommendation.

TechnologiesAzure · Terraform · Infrastructure as Code · Private networking · Managed identities · Key Vault · Monitoring

02

Application delivery automation

Suite Seven

At Suite Seven, I combined backend development with responsibility for the systems used to build, test and deploy Magento and Shopware applications. I built and maintained GitLab CI/CD pipelines and worked with the Linux hosting environments behind them.

What I worked on

  • Maintaining build, test and deployment steps in GitLab CI/CD.
  • Developing Magento and Shopware applications in PHP, which gave me the application context needed when changing a pipeline.
  • Working with Linux environments over SSH for deployment and operational maintenance.

Blue/green deployments were already part of the delivery workflow for larger e-commerce platforms. Not every site used the same deployment model. The available hosting environment, application size and cost of maintaining parallel environments determined whether blue/green deployment was appropriate. Smaller WordPress environments used a simpler approach when an additional test environment and two production environments were not justified.

TechnologiesGitLab CI/CD · Linux · Magento · Shopware · PHP · Deployment automation · Blue/green deployments