towerful@programming.dev 7 months ago
I always think about using nixos. But considering I dockerise everything, I always end up using Debian.
Good old stable Debian
towerful@programming.dev 7 months ago
I always think about using nixos. But considering I dockerise everything, I always end up using Debian.
Good old stable Debian
mobergmann@lemmy.world 7 months ago
You can also use container within NixOS and AFAICT even declare the containers which should be running. Also NixOS is sad to be stable, or am I missing something?
lemmyvore@feddit.nl 7 months ago
Just that compiling packages on a server is not ideal.
corgi@lemmy.world 7 months ago
Nixos will use/download cached binaries that are available in its repo. It has one of the biggest repositories of any Linux distro. It’s on par with Arch with around 90 thousand packages.
Unless you are doing something custom or niche, your nixos won’t have to compile anything.
lemmyvore@feddit.nl 7 months ago
Are all those packages available in binary format? Not familiar with Nix but that’s certainly not the case for Arch. Arch has 85k packages in the AUR as source recipes but not as binaries.
I still think Debian makes a better use case for a server since it provides everything as binaries.
If you’re going to use binaries what’s the point of using Nix anyway? The declarative aspect is nice in an abstract sort of way but you can achieve a system deploy or restore just as fast by installing a vanilla system and a few config files.
towerful@programming.dev 7 months ago
Yeh, but I already have compose files and ansible things to set up a server.
And I’d have to figure out how health checks and depends-on works for that.
I’m sure it would give me an amazing experience, but I have all the tools and I can run them in isolation (ie I can install docker on any os I can SSH into)