It worked—until it didn't.

We moved from running local scripts on a shared Mac to each admin working from their own local repo, committing changes through Git, syncing packages with az git hooks. We used to push changes first, then capture them in Git after the fact. Now, Git is the gate. Commits and PRs drive the entire process. Pipelines run automatically, and the cloud becomes the source of truth. Our local caching servers listen for updates—pulling down only when there are changes—fully inverting the workflow into something distributed, reliable, and scalable. All of it version-controlled. All of it traceable. All of it running on infrastructure provisioned with Terraform.

Every config, every profile, every software assignment that matters tracked in Git. It’s CI/CD deployed, reproducible by design, and logged automatically for traceability.

What This Blog Is About

This blog is about the journey—the migrations, the patterns that emerged, the decisions that held up, and the ones that didn’t. And about the new tools and ideas I'll be building and using along the way.

If you work in endpoint management with DevOps, you’ll find deep dives into:

• CI/CD pipelines that manage device tools, states, and configuration
• Every cloud resource under Infrastructure as Code with Terraform
• Inventory systems that drive deployment logic
• And Git at the center of it all

As I now manage both macOS and Windows endpoints, I’ll be writing about how I'm creating a cohesive, mirrored management system—where both platforms are driven by open source tools, DevOps, and Git, and where admins speak the same language on both sides.

Focused Systems. Grounded in what actually works and scales. Very opinionated.

Let’s get to it.