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.
M6 gave the Main server its own authoritative nameserver — BIND9, configured the way real hosting servers run it: it answers for the domains it hosts and refuses…
Read more →M5 gave the panel real email: an account owner can create mailboxes, change their passwords, and set up forwarders — mail sent to one address delivered to another,…
Read more →M4 was originally scoped as just an app installer — a one-click way to get WordPress onto a provisioned site. Partway into planning it, a fair question came…
Read more →M3 started as “SSL automation” — issue a Let’s Encrypt certificate automatically when an account’s site goes live, no manual step. That part works, and it’s been proven…
Read more →File Manager for the account side is live — upload, download, rename, delete, new folders, scoped to your own account’s files. The part that matters more than the…
Read more →The milestone that proves this is a real hosting panel and not just an admin UI: creating an account now provisions a real, isolated hosting environment. Not a…
Read more →Worth being honest about this one rather than quietly editing history: earlier planning treated “multi-server” as generic web-hosting-node clustering — accounts distributed across an interchangeable pool of machines.…
Read more →Second milestone done the same day as the first — the Controller area now does real work rather than just existing as a shell. What’s working Servers: register…
Read more →Starting fresh on KNJ Panel: a hosting control panel built from the ground up. The goal is a genuinely complete feature set over time — our own provisioning…
Read more →