-
Moving a 19,348-file static site from GitHub Pages to Cloudflare: the numbers the move has to carry
A fresh build is 865 MB and 19,348 files: 97% of one free Cloudflare Worker's file cap. Why the move needs two Workers, and how long that lasts.
-
Deleting a dead cluster: 55,000 lines that still ran in CI
The servers went on October 1, but their 212 files kept running in CI for a month. Removing them took edits to 13 tools that still read the dead tree.
-
Evolving our CI: from a gate nobody trusts to one that means something
A day of CI data: main was red for 19 hours over one field length, and queueing now costs more than compute. Seven changes, ranked, and the first one shipped.
-
Half our repository is 80 MP3 files, and every CI check downloaded them
Our CI guards cloned all 893 MB of the repository to read a few files. Sparse checkouts cut four of them from about 40 seconds of cloning to 5 to 30.
-
Moving a 20,000-file static site to Cloudflare's free plan
Our site outgrew one free Cloudflare Worker by about 100 files. How we split it in two, and redirected the old GitHub Pages address.
-
Should a 1,300-tool static site move to Astro, Rust or TSX?
20,000 files, 1,000 more a day, 1,321 hand-written HTML tools. Where a framework would help this site, and where Rust or Next.js would not.
-
The site checker parsed the same script 7,333 times
Two thirds of the publish check was one subprocess per inline script, for 1,462 distinct scripts. Checking each once took it from 82 to 31 seconds.
-
The test job was redrawing 1,200 share cards every run
A one-page test build of the site took 64 seconds, 45 of them idle while workers drew cards the deploy had cached. Restoring that cache cut it to 17.
-
CI and application bloat: how much is useful and how much is deadweight
A week of CI runs and a byte count of 1,324 products: what is load-bearing, what is dead, and what is useful but noisy.
-
Do our calculator pages fetch files that exist? A sweep of 1,300 pages
We scanned every venture page and script for relative fetch() calls and checked each target exists. none dangling, and a CI check to keep it so.
-
One command for CI and your laptop: removing 418 copies of one workflow
How this monorepo went from 549 GitHub Actions workflows to 131, made its diff-scoped checks run locally, and found which venture tests the old setup never ran.
-
Five tags that quietly split the blog's filter
The blog's tag filter treats red-team and redteam as different tags. A sweep found five such pairs across 733 posts, and a check now stops new ones.
-
A CI check for the marketing claims we promised not to make
A CI tripwire for visible social-proof claims such as "trusted by 10,000 teams", the half of the no-fake-reviews rule that check_jsonld.py did not cover.
-
Alternatives to GitHub Pages for a 15,000-file static site: what switching or adding would buy
Our site is 738 MB of a 1 GB Pages cap, and 56% of it is podcast audio. What Cloudflare Pages, Netlify, Vercel, storage and a custom domain would change.
-
How a Markdown file becomes a page on this blog
Posts are plain Markdown in docs/posts/. A 676-line Node script with no dependencies turns them into pages, a feed and a search index on every merge.
-
The site was not slow to build. It was slow to ship.
Merges took a median 48 minutes to reach this site. The build was 7 of them. What the rest was, and why a faster language or WASM would not have helped.
-
Our test suite drew the same 2,563 pictures five times
A site's test file took 460 seconds, mostly redrawing identical share-card PNGs in each of five builds. An in-process cache cut it to 325, output unchanged.
-
typeof localStorage is not a safe check
Evaluating the localStorage global throws when a visitor blocks site data, so the feature test itself fails. A one-line helper, applied to 990 pages.
-
When GitHub Actions runners run out: telling a starved check from a real failure
Every check failed in 3 seconds with runner_id 0. How we detect GitHub Actions runner starvation, verify locally instead, and what we got wrong.
-
Why our GitHub Pages site now redeploys on every merge
A hand-kept path filter on the Pages workflow kept missing site inputs. We dropped it: 341 merges a day collapse into one build plus one queued.
-
Moving a static site off a self-hosted Kubernetes cluster to GitHub Pages
Why we retired a two-server k3s cluster and serve a static tool catalogue from a gh-pages branch, and the traps in a branch-published Pages site.
-
We almost rewrote it in Rust: one zlib setting halved a 3-minute static site build
Profiling a 3,000-page static site build: 112 of its 182 seconds were PNG compression at zlib level 9. Level 6 cut it to 81 seconds for 9% larger images.