So as with all of my hyperfixations, I think about all the things I want to add to my homelab. Some of the plans around all of these additions haven’t been fully fleshed out, and therefore are not deserving (in their current form) of a whole section. However, I do want to write down what I want to add, and why I want to add them.

• Ansible and IAC - So one thing I have already noticed that will get old quickly is configuring servers. I mentioned in the DNS Server section that I think configuring basic hardening is something that there is zero excuse not to do. I don’t want to let my laziness get in the way of my principles, and thus now is the time to implement ‘Infrastructure as Code’. Several of the YouTubers I follow recommend Ansible for this, namely NetworkChuck, Wolfgang, and Jeff Geerling. I will write more about this when the time comes for me to actually implement it, but this will allow me to automate allot
• Uptime Kuma - As my home-lab grows I want to be able to monitor all of the services that I am running. Uptime Kuma is one of the easiest ways to do this that I know of.
• Git server - I use GitHub as my portfolio, and because of that I really want to avoid cluttering it with things like the files that this website is run on. For that reason I ideally
• Certificate Authority - I will get into why I want to do this more at the time when I actually do it. To keep things simple however, it is mainly because I want to make sure that all my services communicate over HTTPS, and I don’t want to make exceptions for their certificates on individual devices. Yes, I can do that dodgy thing with Cloudflare and subdomains, but frankly, I want my network infrastructure to be self-sufficient.