This is Phase 1<\/strong> of a custom hosting control panel build \u2014 designed to manage hosting, infrastructure, and automation without relying on traditional panels.<\/p>\n Before any UI, dashboards, or shiny features\u2026 we start with something far more important.<\/p>\n A solid, secure, production-ready foundation.<\/strong><\/p>\n This isn\u2019t just about spinning up a server and hoping for the best.<\/p>\n It\u2019s about building something we fully understand, fully control, and can scale without hitting a mysterious wall later labelled \u201clegacy issue\u201d.<\/p>\n No shortcuts. No black boxes. Just doing it properly\u2026 the slightly painful way.<\/p>\n This isn\u2019t just another web project that looks nice until you open the terminal.<\/p>\n The KR0311 Control Panel is being built to:<\/p>\n The entire platform is being built on a solid, proven stack:<\/p>\n This isn\u2019t just a UI slapped on top of a server.<\/p>\n It\u2019s a full infrastructure-driven platform.<\/strong><\/p>\n Which also means\u2026 when something breaks, it\u2019s definitely our fault.<\/p>\n This control panel is being built inside a dedicated internal environment.<\/p>\n Nothing public. Nothing exposed. No unnecessary risk.<\/p>\n This gives full control, isolation, and the freedom to break things safely\u2026 which, let\u2019s be honest, is absolutely going to happen.<\/p>\n Security isn\u2019t something being bolted on later after a mild panic.<\/p>\n It\u2019s part of the foundation from the very beginning.<\/p>\n The system was configured with:<\/p>\n This ensures the platform is secure before any application code is even deployed.<\/strong><\/p>\n Because nothing ruins your day quite like securing a system after it\u2019s already been \u201cvisited\u201d.<\/p>\n This stage of the custom hosting control panel build focuses on getting everything stable, secure, and ready for future automation.<\/p>\n This phase lays the foundation for the custom hosting control panel build, ensuring everything is stable before moving into application-level development.<\/p>\n With the base system secured, the next step was installing a clean, production-ready stack.<\/p>\n Nothing flashy \u2014 just reliable components that won\u2019t randomly ruin your evening later.<\/p>\n A fast, lightweight, and production-proven web server used to serve the application.<\/p>\n Basically: it just works\u2026 which is exactly what we want.<\/p>\n The latest stable PHP version compatible with Laravel.<\/p>\n Installed with required extensions including:<\/p>\n No missing extensions. No mysterious white screens. No guessing games.<\/p>\n A secure and reliable database engine configured with:<\/p>\n In other words: none of the stuff you forget about until it becomes a problem.<\/p>\n Redis is being introduced early so we don\u2019t have to awkwardly bolt it on later when everything already depends on something else.<\/p>\n It will power:<\/p>\n Used to manage Laravel dependencies and PHP packages globally.<\/p>\n Without it, nothing works. With it, everything works\u2026 until you update something.<\/p>\n Installed to support modern frontend tooling such as:<\/p>\n Because at some point, the frontend will absolutely demand it.<\/p>\n For reference, the official Ubuntu Server documentation is available here: Ubuntu Server documentation<\/a>.<\/p>\n Additional tools installed include:<\/p>\n Getting the stack installed is one thing.<\/p>\n Making sure it\u2019s secure before anything else touches it is where most people start cutting corners.<\/p>\n We didn\u2019t.<\/p>\n With everything in place, the next step was tightening it all down.<\/p>\n This is about reducing risk now \u2014 not firefighting later at 2am.<\/p>\n Only trusted access. No guessing. No brute force attempts getting lucky.<\/p>\n Only essential ports are open right now:<\/p>\n Everything else is blocked by default.<\/p>\n This is deliberate.<\/p>\n At this stage, the system is still evolving \u2014 so we\u2019re keeping the attack surface as small as possible.<\/p>\n As new services are introduced later, only the required ports will be opened \u2014 nothing more, nothing less.<\/p>\n No \u201copen everything and see what happens\u201d strategy here.<\/p>\n Fail2Ban is active and monitoring login attempts, automatically blocking suspicious activity.<\/p>\n If something starts hammering the server, it gets shut down pretty quickly.<\/p>\n As it should.<\/p>\n Before moving forward, everything was tested to confirm a clean working environment.<\/p>\n If anything was broken at this stage, now was the time to find out \u2014 not three phases later when everything depends on it.<\/p>\n At this point, the system is no longer \u201cjust a VM\u201d.<\/p>\n It\u2019s a fully operational application platform.<\/strong><\/p>\n Which is both exciting\u2026 and slightly dangerous.<\/p>\n This phase might not look exciting from the outside \u2014 no UI, no dashboards, nothing flashy.<\/p>\n But this is where most projects quietly set themselves up for failure.<\/p>\n By doing this properly, we now have:<\/p>\n Everything moving forward builds on this.<\/p>\n This is where most people rush.<\/p>\n We didn\u2019t.<\/strong><\/p>\n Future us will be very grateful for that.<\/p>\n At this point, the custom hosting control panel build has a stable and secure foundation to build on in the next phase.<\/p>\n With the base system complete, the next step is where things start to come to life.<\/p>\n Phase 2 will include:<\/strong><\/p>\n This is where things stop being \u201cinfrastructure\u201d and start becoming an actual product.<\/em><\/p>\n Every platform starts somewhere.<\/p>\n This is the first real step in building the KR0311 Control Panel \u2014 not just as an idea, but as a working system.<\/p>\n Built properly. Built securely. Built to scale from day one.<\/p>\n No shortcuts.<\/p>\n Just a solid foundation\u2026 and a lot more work to come.<\/p>\n This project is being built step by step as part of the KR0311 Control Panel series.<\/p>\n If you want to follow along:<\/p>\n Each phase builds on the last \u2014 from infrastructure and provisioning through to a fully functional hosting platform.<\/p>\n","protected":false},"excerpt":{"rendered":" Phase 1 of the KR0311 Control Panel build: Ubuntu setup, security hardening, and installing the core stack that forms the foundation of the platform.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[19,20,10,29,13,26,24,25,27,28,21,23,22],"class_list":["post-37","post","type-post","status-publish","format-standard","hentry","category-control-panel","tag-control-panel","tag-custom-hosting-control-panel","tag-homelab","tag-hosting-infrastructure","tag-linux","tag-mariadb","tag-nginx","tag-php","tag-redis","tag-security-hardening","tag-self-hosted","tag-server-setup","tag-ubuntu"],"_links":{"self":[{"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/comments?post=37"}],"version-history":[{"count":4,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/posts\/37\/revisions"}],"predecessor-version":[{"id":87,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/posts\/37\/revisions\/87"}],"wp:attachment":[{"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/media?parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/categories?post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kr0311.com\/projects\/wp-json\/wp\/v2\/tags?post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n\ud83e\udde0 What is the KR0311 Control Panel?<\/h2>\n
\n
\n
\ud83d\udda5\ufe0f Development Environment Setup<\/h2>\n
\n
![\"custom](\"https:\/\/kr0311.com\/projects\/wp-content\/uploads\/2026\/04\/Development-Rack.jpeg\")
\n <\/figcaption><\/figure>\n\ud83d\udd12 Security First \u2013 Not an Afterthought<\/h2>\n
\n
\u2699\ufe0f Core Stack Installed<\/h2>\n
\ud83c\udf10 Nginx Web Server<\/h3>\n
\ud83d\udc18 PHP 8.3 (PHP-FPM)<\/h3>\n
\n
\ud83d\uddc4\ufe0f MariaDB Database<\/h3>\n
\n
\u26a1 Redis (Caching & Queues)<\/h3>\n
\n
\ud83d\udce6 Composer<\/h3>\n
\ud83e\uddf0 Node.js & npm<\/h3>\n
\n
\ud83d\udd27 Supporting Tools<\/h3>\n
\n
\n\ud83d\udd10 Hardening the System<\/h2>\n
\ud83d\udd10 SSH Lockdown<\/h3>\n
\n
\ud83d\udd25 Firewall Strategy (UFW)<\/h3>\n
\n
\ud83d\udeab Fail2Ban Protection<\/h3>\n
\ud83e\uddea Service Validation<\/h2>\n
\n
\ud83e\uddf1 Why This Phase Matters<\/h2>\n
\n
\n\ud83d\udd1c What\u2019s Next \u2013 Phase 2<\/h2>\n
\n
\n\ud83d\udccc Final Thoughts<\/h2>\n
\ud83d\udd17 Follow the Build<\/h2>\n
\n