nginx – Türker Yıldırım

The second host, and the failover we finally built

Deep diveMarch 27, 202614 min read

Seven years on one host, and a business requirement that finally arrived. A recovery time that assumes the host comes back.

nginx as the only thing holding a certificate

NoteMarch 19, 20262 min read

A certificate loaded by one process, and a reload that had to work for the renewal to take effect. Three steps, of which the first two report success…

The incident that was a certificate, again

Deep diveOctober 10, 202510 min read

The third certificate incident in six years, each with a different cause. An expired certificate on a service nobody remembered was serving TLS.

Docker Compose in production, and why it is still here

Deep diveSeptember 19, 202510 min read

Six years of Compose on a VPS, and an annual conversation about orchestration. Nothing is wrong, which is why the conversation keeps happening.

A rate limit in nginx that should have been in the application

NoteJune 20, 20251 min read

A limit keyed on the client address at the edge, protecting an endpoint whose consumers are authenticated and identifiable. The edge knows the address and the application knows…

nginx 1.28, and enabling HTTP/3 on purpose

NoteMay 21, 20252 min read

HTTP/3 support has been present and experimental for a while, and the April stable release made enabling it a decision rather than a gamble. The Alt-Svc header is…

The VPS that had been running since 2019

Deep diveFebruary 28, 202514 min read

A host provisioned in 2019, upgraded in place three times, and a provisioning script that has never been run against an empty machine.

nginx 1.26, and a config that needed nothing

NoteMay 27, 20242 min read

The stable branch moved in April and the configuration required no changes, which is worth writing down as often as the opposite. The http2 on directive is the…

The registry we ran ourselves for three weeks

Deep diveMarch 27, 202410 min read

A rate limit hit at 09:00 every weekday, a pipeline failing intermittently for two months, and the wrong one of three options tried first.

The alert that fired for two years and meant nothing

Deep diveOctober 18, 202310 min read

Thirty-one alert rules, a channel muted by everybody, and 412 alerts in a month of which four corresponded to a real problem.