Hey everyone!
I have been building and maintaining my own infrastructure around self-hosted Linux services for months. Eventually I got annoyed with editing and deploying everything manually and having difficulties sharing what I’m doing with others. So I solved both of these problems with Infrastructure as Code.
Everyone is free to study this repository. Ever wanted to see IaC in practice? Curious how to self-host certain services, automate website deployment from Git to server, make TLS SNI-based router or automate container provisioning? Then this repository is for you.
Want to know how much CPU, RAM or other resources a certain service has? You can see it yourself on my own public dashboard.
This is the first time I share my infrastructure with anyone. I’d be more than happy to discuss it, receive feedback and answer question. In the meantime, I’m writing an article to complement the code with architecture, decisions and thought behind it.
Unless you can 100% guarantee that there are no security flaws whatsoever in your Infra, I wouldn’t do this.
100% guaranteed security is literally impossible, nobody on the planet can guarantee that about anything. IDK if you realize but you’re basically arguing against FOSS security solutions.
Do you mean we Lemmy users shouldn’t do this, or IaC shouldn’t be done in homelab? I don’t understand your objection.
obscurity != security
that said, you gotta be safe and make sure you’re not committing keys, passwords, etc.
there is never a 100% security guarantee.
Exactly my approach!