Welcome to the e4z Blog
Kicking off the e4z blog — what to expect, why it exists, and what I'm working on.
Hey — welcome in.
This is the first post on the e4z blog. The main site (the one you probably came from) is a showcase of the little web projects I've been shipping: cake sites, security camera installers, auth starters, and a few more. I needed somewhere to write down the stuff that doesn't fit on a pricing page.
What goes here
Four-ish buckets:
- Homelab and self-hosting. Saltbox, Docker Compose, Cloudflare Tunnels, weird DNS bugs.
- Web dev. Next.js 16, React 19, the quiet parts of moving between Vercel, Cloudflare Pages, and Workers.
- Dev logs. Half-finished ideas, things that broke, things that finally worked.
- Tooling. CLI utilities, notification pipelines, the unglamorous scripts that glue everything else together.
No schedule. No newsletter. No ads. Just posts when I actually have something to say.
Why a static blog
The entire blog is:
content/blog/*.md → Next.js static export → Cloudflare Pages
Every post is a plain markdown file in the repo. Pushing is git commit + wrangler pages deploy. No database, no CMS, no admin panel to forget the password to. If I ever want to leave this stack I can rsync the markdown somewhere else in thirty seconds.
What's next
A few posts already queued up:
- A write-up of how
moviestats.xyzis hosted (short version: Cloudflare Tunnel to a Saltbox box — and the day it went down). - Notes on shipping Next.js 16 to Cloudflare Pages without
@opennextjs/cloudflarefighting you. - The first of an ongoing dev log on whatever I'm currently breaking.
Bookmark it, or don't — the RSS feed is coming in v2.
See you around.