LEARNING IN THE OPEN
What I’m building, what’s breaking, and what I’m learning.
A running journal of DevOps and platform engineering.
This week was about making operational boundaries explicit and giving the build system enough dedicated capacity to be dependable. The work crossed the GitOps, infrastructure-as-code, deployment-server,…
This week I concentrated most of my development time on DurpDeploy. The work moved the deployment system from a collection of capable execution paths toward a more deliberate operational control plane:…
This week was a cleanup and hardening week across the homelab rather than a week for a single new platform service. The GitOps repository received six commits across eighty files and all four environment…
This week was split between moving the homelab’s source-control direction toward Forgejo and making DurpDeploy’s remote-agent model more useful under real deployment conditions. The GitOps repository…
This week I concentrated the homelab work in the GitOps repository, with eighteen commits across twenty-six files and changes spanning the infra and dmz environments. The visible changes touched Argo CD,…
This week was mostly about making the homelab’s platform layer more predictable. I finished bringing Forgejo onto CloudNativePG, added Harbor as the internal registry and cache layer, tightened a few…
This week was primarily about making the DMZ cluster more useful without making it less understandable. I added two services to the GitOps graph, SearXNG and an Authentik remote-cluster outpost, then worked…
This week I moved two related pieces of the homelab forward. The larger change was an infrastructure-as-code bootstrap for the DMZ Talos environment and a more explicit Argo CD ownership model for the…
This week was split between identity work in DurpDeploy and a fairly consequential cleanup of the GitOps repository that describes the homelab. The headline feature is OIDC single sign-on for DurpDeploy,…
Another busy week across the homelab stack. The big themes this time around are security hardening in DurpDeploy (a batch of fixes that came through the GitHub-to-GitLab sync pipeline), a major new database…
The biggest piece of work this week landed on Tuesday, July 29. Commit a7f6a339 introduced a complete JSON REST API surface for DurpDeploy, spanning roughly 104KB of diff across dozens of files. This is not…
Two projects had activity this week. The durpdeploy repo saw the bulk of the work – a feature blitz that started July 20 and ran through July 25, shipping GitHub Actions pipeline fixes, a notification event…
This was a heavy week for durpdeploy. Four P1 features landed back-to-back on July 17-18, followed by the backup-restore runbook on July 19. The full P1 list – per-project authorization, admin user…
The headliner this week is the creation of the dmz-talos environment – a full Talos Linux-based DMZ cluster that mirrors the existing dmz environment running on the older infrastructure. Commit bf62068c on…
One commit landed in the gitops repo this week, updating the DMZ environment’s internalproxy configuration. The change added Kubernetes Endpoints and Service definitions for a new Hermes VM at…
This week I kicked off durfy/apps/durpdeploy , a new Go-based deployment utility, and it dominated my commit log – 19 commits over three days. That is a furious pace for someone who usually averages a…
This past week, I focused on hardening the Infra-v2 stack to improve reliability, focusing on GitOps-driven delivery, high-availability networking, and enterprise-grade storage provisioning. The goal was to…
The core tenet of DevOps is treating infrastructure as code. While building a Kubernetes cluster with standard tooling is achievable, the process invariably leads to the greatest pain point for any…
As a DevOps Engineer, my job often revolves around building resilient, automated, and scalable systems. The theoretical knowledge is vast, but the true learning happens when theory meets reality—and the…
Try a different search or choose another topic.