Skip to main content

        System Reboot: Migration to Hugo and the New Knowledge Base - Featured image

System Reboot: Migration to Hugo and the New Knowledge Base

Every good SysAdmin knows that there comes a point in the life of any infrastructure where continuing to patch legacy systems is no longer viable. It’s time to perform a wipe, redesign the architecture, and redeploy from scratch.

Welcome to the new mxlit.com.

The Paradigm Shift: Goodbye to the Heavyweight CMS

For a long time, I maintained this space on traditional platforms, but as an Infrastructure Engineer, the idea of ​​having databases running, exposed ports, and vulnerable plugins to serve simple text went against everything I apply in my daily work.

Therefore, this site has been rewritten from the ground up, applying a strictly Zero-Touch and Defense in Depth philosophy:

  • Frontend: Statically generated with Hugo. Zero databases, millisecond load times.

  • Backend: An isolated Nginx container on Alpine Linux.

  • Security: 100% of traffic routed through Cloudflare Tunnels (Zero Trust). The server does not have a single port open to the internet.

  • CI/CD: Automated deployments via GitHub Actions. I do a git push and the infrastructure takes care of the rest.

From Obsidian to the Web: The Knowledge Base (KB) is Born

The main goal of this reboot isn’t just to write for the sake of writing. In my day-to-day work managing complex corporate environments, Exchange, migrations, PowerShell automations, Backups architectures, I generate a lot of technical documentation that’s locked away in my local Obsidian vault.

Starting today, I’ll begin a gradual migration process to export that documentation and publish it here under the KB (Knowledge Base) naming convention.

The goal is simple: to create a robust, evergreen, and frictionless technical repository. If an automation script or a Proxmox troubleshooting tool saved my weekend, it’s very likely it will be useful to another engineer out there.

What’s Next

In the main section, you’ll see a mix of quick updates (like this one) and in-depth technical articles.

The production environment is stable, containers are running smoothly, and automated deployments are flowing. It’s time to start transferring the data.



End of transmission.