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.
The customer’s File Manager problem was fixed twice before it was actually fixed. Both times the tests passed. The reason is worth writing down. Three places it worked…
Read more →After a customer’s bug report was fixed, we decided to go beyond a fix: stop patching the File Manager and build the one it should have been, with…
Read more →A customer’s own bug report arrived through the person who runs the server: uploads into some folders did nothing, the code editor opened blank, and saving any file…
Read more →The Traffic & Visitors page had been empty for weeks, while the same site was gaining subscribers every day. Nothing was reporting a problem, which was the problem.…
Read more →Sign-ups for the panel’s own update list had started arriving on their own. That is the moment a manual process stops being fine. The export-import routine The panel…
Read more →The last two audits looked at the server itself, from the point of view of one hosting customer curious about their neighbours. Readable by default Some things a…
Read more →The second audit found the most significant issue of the day, and it came from a sensible design choice. Quarantine in the wrong place When the malware scanner…
Read more →The first of four security audits in one day started with a question about something ordinary: where does the link in a password-reset email actually come from? Built…
Read more →The first real test of the new backup schedule failed before it started — not because anything broke, but because the system was certain it had already done…
Read more →A safety check that rejects something harmless is a bug, even if it’s the safe kind of bug — because the cost is a restore that fails on…
Read more →