|
|
|
|
|
|
by RadiozRadioz
651 days ago
|
|
|
I want to achieve a FLOSS setup of my personal infrastructure that can completely replace the things I use proprietary software for. I want to put in the hard work now so that I can leave it as-is indefinitely and I never have to be bitten by "sorry we're shutting down this service" or "hey, we redesigned the whole UI for fun!" or "you must download this update or your service will stop working". |
|
|
Deploying FLOSS software on your own infra can also be a good way to contribute something back: there are usually some things you need to do for your setup that aren't yet covered by the project itself. Eg, I just deployed an open-source RSS reader on a private k8s cluster and didn't yet have a Helm chart. So I will make that open source for whoever wants to deploy that same RSS reader on k8s without having to reinvent the wheel.
Deploying everything on k3s running on dedicated servers has also been a great way to better understand how Kubernetes works. Coming from the AWS world, it's an interesting challenge—there's so much I have to figure out now that AWS used to handle for me (PKI, load-balancing, private DNS, etc).