Blog
Articles on CI/CD pipelines, Docker, Kubernetes, cloud infrastructure, and observability — practical DevOps engineering notes from real production systems.
138 articles
DevOpsA managed platform hands you a browser log stream instead of a shell. Structured JSON, correlation IDs, stdout buffering and the checklist that has to be true first.
Read More
A rolling deploy runs the old release and the new one against one schema for a window you do not control. The deploy mechanics that decide what a migration may do.
Read More
A platform builder is created for your deploy and destroyed after it, so every layer is cold unless you arrange otherwise. Layer order, build context, cache mounts and the registry cache that actually travels.
Read More
A plugin upgrade does not break the build. It changes how the agent behaves, silently, mid-sprint. How to pin a version, notice a move, and roll back.
Read More
A plugin release can install cleanly and ship half a bundle. Here is the GitHub Actions pipeline that gates it: strict manifest validation, the paths and hook scripts nobody checks, a behaviour gate built from the headless CLI, and tagging that survives a failed push.
Read More
What an AI DevOps assistant genuinely shortens during Kubernetes triage — correlating a restart with a deploy, telling OOMKilled from CrashLoopBackOff — and the faults it cannot see.
Read More
n8n and Flowise both deploy in one click on a platform billed in rupiah. Neither survives its first redeploy without a persistent volume, a public webhook URL, a pinned encryption key and authentication.
Read More
The repository signals a PaaS build engine reads to generate a Dockerfile, the four cases where auto-detection guesses wrong, and the override I keep committed.
Read More
Claude Code reads dozens of environment variables. Here are the ones worth setting on a build agent, and the three with side effects you did not want.
Read More
Six variables give you per-user cost, token and tool telemetry. The interesting part is which attributes the cost metric carries, and what content logging asks of you.
Read More
The allowlist behind a working install, the shell exports that never reach background agents, and the one setting that is actually validated at startup.
Read More
A dev container gives every engineer the same bounded environment. Here is the authentication that survives a rebuild, the egress firewall, and the limits of the isolation.
Read More
The GitLab integration is one job and one masked variable. The parts that stall teams are the mention trigger you have to build and a PATH line in the installer.
Read More
Session-scoped loops, cloud routines and desktop tasks solve different problems. Here is which to reach for, plus the jitter and expiry rules that surprise people.
Read More
A self-hosted environment executes Claude Code cloud sessions on your own hosts, with every connection outbound and no inbound port for Anthropic to reach.
Read More
A hardened container, cron workstreams, credentials that survive a sanitised environment, and the resilience layer that keeps an unattended agent alive.
Read More
Letting an agent merge its own pull requests safely: a pre-tool hook that blocks the merge if the test count dropped or tests were skipped to go green.
Read More
Using an AI agent during an incident without letting it make things worse: evidence before hypotheses, testing the origin not the CDN, and hooks that block.
Read More
AI code review tools split into terminal agents, platform bots, and dedicated services. Here is how the categories differ and how to pick for your team.
Read More
Run several Claude Code sessions at once without collisions by giving each its own git worktree, plus how to isolate ports and dependencies and when parallelism pays.
Read More
How the Claude Code GitHub Actions integration turns an @claude mention into a reviewable pull request, and how to keep an automated contributor safely in review.
Read More
How Claude Code headless mode runs the agent non-interactively with claude -p, so you can wire it into CI/CD, restrict its tools, and read structured output.
Read More
Helm 4 is the first major release in years. Here are the real breaking changes — server-side apply, the new plugin system, registry login — and my migration checklist.
Read More
How I load test Node.js APIs with k6 — writing tests, VUs and stages, thresholds as CI gates, streaming to Grafana, and finding the DB connection-pool ceiling.
Read More
