Notes from building KNJ Panel, in the order it actually happened.
blog /blɒɡ/ noun — 1. A web log. 2. Here: a build log. What we built, what broke, and what we learned.
“Server time” is one of those phrases everyone is sure they understand. A backup was set to start at 02:00, the settings page said “server time (UTC)”, and…
Read more →A feature can pass every test it has and still never have worked once. This is the story of a backup feature that, in a real run on…
Read more →A backup server exists so that backups aren’t stored on the web server. Until now, the panel also kept its own full copy there. Mirror, not move Every…
Read more →The first fix for a bug is often not the last one. This is the story of a workaround that failed for a reason nobody had found yet.…
Read more →Some bugs are silent because the thing protecting against them is doing exactly its job. A self-repair that assumed too much Older accounts’ configuration gets upgraded automatically, so…
Read more →A bug that was already fixed once has a particular way of being annoying the second time. Nobody’s looking for it. The fix is already filed away as…
Read more →A tidy-up step is supposed to be the safe part. Sweep away whatever’s left lying around, leave the real thing behind. Nobody writes a broom that asks first.…
Read more →Handing a domain over sounded like the last step. It kept turning out to be the second-to-last one. What a promise to answer actually requires A domain delegated…
Read more →A banner said the same thing every time someone logged in: this address is borrowed, choose your own. Clicking through it landed on a form asking for a…
Read more →The setup wizard says it, clearly, the very first time anyone reaches it: this name won’t last, choose your own. And then the wizard finishes, and it never…
Read more →