Comment on Selfhosted photo manager kind of like Jellyfin
Atemu@lemmy.ml 8 months agoThis is a false dichotomy. Just because containers make it easy to ship software, doesn’t mean other means can’t be equally easy.
NixOS achieves a greater ease of deployment than docker-compose and the like without any containers involved for instance.
Nibodhika@lemmy.world 8 months ago
NixOS packages only work with NixOS system. They’re harder to setup than just copying a docker-compose file over and they do use container technology. If the idea is to remove complexity from the setup, NixOS goes in the opposite direction.
Also without containers you don’t solve the biggest problems such as incompatible database versions between multiple services.
I stand by what I said, I can give a 2 step tutorial on setting up any docker system (copy this compose file, run up on it), anything simpler than that wouldn’t be as robust in terms of configurations.
Atemu@lemmy.ml 8 months ago
It’s interesting how none of that is true.
Nixpkgs work on practically any Linux kernel.
Whether NixOS modules are easier to set up and maintain than unsustainably copying docker-compose files is subjective.
Neither Nixpkgs nor NixOS use container technology for their core functionality.
NixOS has the
nixos-containerframework to optionally run NixOS inside of containerised environments (systemd-nspawn) but that’s rather niche actually. Nixpkgs does make use of bubblewrap for a small set of stubborn packages but it’s also not at all core to how it works.Totally beside the point though; even if you don’t think NixOS is simpler, that still doesn’t mean containers are the only possible mean by which you could possibly achieve “easy” deployments.
Ah, so you have indeed not even done the bare minimum of research into what Nix/NixOS are before you dismissed it. Nice going there.
Docker compose is about the opposite of a robust configuration system.