← Back to Field Notes

Series · 4 notes

The golden image

The server image every Infinary site runs, and how we keep it current, reproducible and tested.

  1. Part 1 Deep dive Aug 25, 2026

    The same image under two names nearly ran a migration

    On August 25 we moved our update pipeline from image tags to digests. Naming the image our site already ran by its digest made our own update logic treat it as a new release, ready to back up and migrate onto itself. We reverted in four minutes; nothing ran.

  2. Part 2 Deep dive Oct 12 – 16, 2026

    Chrome PDFs couldn't run on any of our sites

    A question about why a PDF from the phone looked different led to a bigger find: Chrome, which ERPNext 16's own report formats use, couldn't start on any Infinary site. We baked a pinned Chrome into the image and made it every site's PDF engine.

  3. Part 3 Deep dive Oct 11 – 18, 2026

    Keeping our golden image on the newest Frappe and ERPNext

    Twice in six days we moved every site's base image to the newest ERPNext and Frappe v16, and upstream re-pushed a tag under us in between. How we pin, check and test an upgrade, what that caught, and the nightly job we wrote so it stops depending on someone remembering.

  4. Part 4 Deep dive Oct 19 – 20, 2026

    The golden nightly's first real runs found three bugs

    We built a nightly job that assembles candidate server images whenever anything upstream changes. Its first real runs found three bugs that no test had: a parser that only understood JSON, an error sent to /dev/null, and a promote rule that could never pass.