Devops

Every project I’ve touched in the last decade has a .env file. Sometimes it’s .env.local. Sometimes .env.development. Sometimes it’s the same file, committed to the repo, with a # DO NOT COMMIT comment at the top. That comment has never once stopped anyone. .env files are a solved problem that everyone keeps solving badly. The file format is fine. The habit of scattering them across projects, laptops, and Docker volumes — and then treating them like source code — is where things go sideways. A committed .env is a leaked secret. A .env emailed to a new teammate is a secret with no single point of revocation. A .env that lives on your laptop for two years is a secret you’ve forgotten about. ...

I wanted a simple blog: write a Markdown file, push to GitHub, and have it live on my domain within a minute. No CMS, no server to maintain, no monthly bill. Here’s exactly how I built it. The Stack Hugo — static site generator. Builds the entire site in under 100ms. PaperMod — clean, fast Hugo theme with dark mode, tags, and RSS out of the box. GitHub — source of truth. Every push triggers a deploy. GitHub Actions — builds the site and deploys it on every push to master. Cloudflare Workers + Assets — hosts and serves the static files globally. Free tier is more than enough for a personal blog. Cloudflare DNS — manages the custom domain with automatic SSL. Total cost: zero. ...