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 biggest gap left on the parity list was migration: a way to bring an account off a cPanel/WHM server onto KNJ Panel. The panel already had one…
Read more →Challenge-response has been working for a while: a server-side mail rule diverts anyone not on the allow list into a Pending folder. But approving a sender only changed…
Read more →Two phases ago, Perl Modules and PHP PEAR Packages moved off the web request path and onto the queue worker, because installing a brand-new package can need to…
Read more →Backup Restoration has always meant one thing: wipe the account’s home directory and re-extract the whole files archive. That’s correct but blunt, and per-file and per-directory restoration needed…
Read more →The previous phase closed out PHP PEAR Packages by widening the web application’s hardening allowances for two new locations. Before trusting that fix, we checked something flagged but…
Read more →The last open item under Backup & Server Status: which accounts get backed up on the automated scheduled run. Previously the answer was “all of them, always”, with…
Read more →The last open item in the Client Panel’s Software section was PHP PEAR Packages. The obvious shortcut was to guess a curated set from PEAR’s channel naming convention…
Read more →The admin-side Perl Module Manager (Phase 78) already did the real work: a curated set of 8 common CGI modules, install state read live off the server, and…
Read more →Upgrading the database server’s major version is the kind of admin action where a wrong guess doesn’t just break a feature. So this one started with research: what…
Read more →The largest item still open on the gap list was Statistics Software Configuration. The existing Traffic & Visitors page already parses access logs for requests, unique visitors, response…
Read more →