Post

after using nixos for a couple years now im not convinced that nix modules are the correct solution for infra deployment. why are we throwing out all of the work done by upstream maintainers on e.g. docker compose? why are we not using containers in general?

Schromp

@schro.mp

8 Sept

why do we have a module abstraction over the top of upstream config options?

Schromp

@schro.mp

8 Sept

if you care about high availability deployments you basically have to reinvent everything. Id rather build on a existing orchestrator.

Schromp

@schro.mp

The conclusion im arriving at is that i will probably: - Use nix for packaging (what its best at) - Use nixos for the base - Setup k3s using nixos - In cases where i dont want the complexity of Kubernetes use docker compose from upstream

8/9/26, 3:05 pm0 reposts0 likes

Schromp

@schro.mp

8 Sept

Regarding the complexity of Kubernetes: This is also widely overstated on every social platform. If you have a little knowledge and are careful to not pull in too many dependencies Kubernetes can be pretty simple and make your life super easy

Schromp

@schro.mp

8 Sept

Idk if this is the actual best way to go but i guess well see after i tested this for a bit