This wiki serves as a central knowledge base for my personal networking infrastructure, covering everything from Docker stacks and virtual machines to routing within my autonomous system. Over the years, I’ve accumulated many configurations and templates that have helped me design, operate, and troubleshoot complex systems. Instead of letting that experience remain fragmented across notebooks, shell histories, and random files, this documentation is my attempt to consolidate everything into a structured, searchable format in order to both remember and distribute.
The primary audience for this wiki is myself, but I’ve written it in a way that should also benefit other engineers, hobbyists, and homelab enthusiasts. Whether you’re trying to replicate weird SAML authentication, find niche regex for a Traefik rule, or simply configure a clean and maintainable VM environment, this resource should provide you with practical insights grounded in real-world deployments.
This wiki is divided into several sections, each focusing on a different layer of my infrastructure. While many networking wikis only document “what” was deployed, I’ve made an effort to also capture the “why” behind design decisions. My hope is that this will not only serve as a technical reference, but also as a record of architectural reasoning that can guide future changes.
docker-compose.yml files, stack deployment patterns, and troubleshooting notes.One of the guiding principles of this documentation is repeatability. I aim to document not only the final configurations but also the steps required to get there. That way, when I revisit a setup months (or years) later, I can rebuild from scratch without guesswork. Where possible, I’ve leaned on infrastructure-as-code principles, using tools like Ansible to define declarative states. However, I also include manual approaches when they’re more practical or when automation adds unnecessary complexity.
Another key value is transparency. Networking can be a black box, especially when vendor defaults obscure what’s really happening under the hood. This wiki attempts to peel back that layer by documenting configurations in full, noting what each setting does, and explaining why it was chosen. This makes troubleshooting far easier and helps prevent configuration drift over time.
Finally, this is a living document. Infrastructure evolves, new tools emerge, and best practices shift. I expect this wiki to grow alongside my deployments. Each entry is a snapshot in time, but together they form a narrative of ongoing experimentation, improvement, and learning.
If you’re new here, I recommend starting with the Infrastructure Overview, which provides a high-level diagram and explanation of how all the components fit together. From there, you can drill down into specific areas such as Docker stacks, VM environments, or routing policies.
Happy exploring, and may this documentation serve as both a reliable reference and a source of inspiration for your own networking journey.