deployment – Page 15 – Türker Yıldırım

The moved block that saved a destroy and recreate

NoteFebruary 2, 20232 min read

Renaming a resource in the configuration is a destroy and a create as far as the plan is concerned, and on a database that is a very bad…

The Dockerfile that finally stopped installing the world

Deep diveJanuary 25, 20238 min read

A 1.4 GB image and a six-minute build, for an application that is 40 MB of PHP. Most of it is build tooling that shipped by accident.

Blue-green on one host, which is two directories

NoteJanuary 24, 20232 min read

The pattern does not require two machines, a load balancer or an orchestrator — it requires two copies and a pointer. mv -T on a symlink is atomic…

A systemd restart policy that hid a crash loop

NoteJanuary 18, 20232 min read

A worker that had been restarting every 40 seconds for eleven days, reported as active by every check that looked. Restart=always with no burst limit converts a hard…

Larger runners, and the pipeline that was memory-bound

Deep diveDecember 13, 202210 min read

October, larger runners, and a build that was swapping. A Node build that used 6 GB on a 7 GB runner.

The webhook we sent, and the retries we owed

Deep diveDecember 7, 202210 min read

Being the sender, for the first time, and the obligations that come with it. A customer endpoint that was down for six hours.

Matching the container uid to the host at build time

NoteNovember 25, 20222 min read

Passing the host uid as a build argument makes the container write files the developer owns, at the cost of an image that is specific to one machine.…

A pipeline that only builds what changed

Deep diveNovember 15, 202210 min read

A 22-minute pipeline on a repository where most changes touch one directory. Every push runs everything, including the untouched.

Importing what already exists, one resource at a time

NoteNovember 11, 20222 min read

Adopting Terraform on existing infrastructure is mostly import, and import brings a resource into state without writing any configuration for it. One resource, one commit, one empty plan…

A queue worker that scales on the metric that matters

Deep diveNovember 9, 202210 min read

Six workers, always, whether there is work or not. A backlog at 09:00 and idle capacity at 03:00.