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?

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

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

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

0 reposts0 likes

No replies yet.