Welcome.
I’m Aaron — a network engineer focused on cloud, identity, and infrastructure. This site is a collection of projects, writeups, and notes from the field.
Alright. Let’s reset the narrative.
If your “home lab” started with Docker Compose and a YouTube tutorial titled “10 Services You NEED to Self-Host” — you skipped the hard part.
And the hard part is the part that actually matters.
A real home lab doesn’t begin with containers. It begins at the edge. It begins with control. It begins with infrastructure.
A practical guide for deploying a locally developed Hugo site to Azure Static Web Apps using GitHub Actions.
So now the site exists. The theme is wired up. The local server is humming along on localhost:1313.
And then you hit the real question:
How do you actually post something?
This is where Hugo stops being “a static site generator” and starts being a habit. Writing posts is the entire point, so let’s document that workflow while it’s still fresh in my head.
No cloud, no deployment pipelines, no polish. Just creating content and seeing it live on a locally hosted Hugo site.
Hey there, fellow tinkerer. If you’re anything like me—a developer who’s spent too many late nights wrestling with bloated CMSes—you know the thrill of stripping things back to basics. Static sites? They’re the minimalist’s dream: fast, secure, and zero server-side drama. Today, I finally carved out time to dip my toes into Hugo, the Go-powered static site generator that’s been on my radar for years. No more excuses. This post is my raw, unfiltered log of the setup process. Think of it as a breadcrumb trail for anyone following in my footsteps. Let’s break it down, step by step, because if I’m doing this once, I might as well make it repeatable.