I meant more figuratively. Finally managed to move my compose files to nix files thanks to compose2nix. One thing that throw me for a loop was that podman (or perhaps nix) creates a service named <backend>-<service>. Compose2nix handles this accordingly but I had a few hours of head scratching until I figured that out.
Comment on What's up, selfhosters? It's self hosting Sunday!
Laser@feddit.org 3 weeks agoNixOS […] learn everything
I don’t think it’s possible to learn everything for NixOS as a casual user / admin. It’s massive. I was luckily able to sneak a NixOS project into work which gave me some paid time on the topic. But there’s always room to learn more about it. Which is a good thing - by its nature, it’s just more powerful than conventional distributions.
uranibaba@lemmy.world 2 weeks ago
Laser@feddit.org 2 weeks ago
Good luck on the journey! What I meant is that over time, you’ll realize that what you did was probably not the most elegant was to do something, at least that’s my experience with my config. Like, I started with a flake with an explicit config for each machine (basically multiple nixosConfigurations) and then turned it into a lib with functions to turn a set of hosts from json into an attribute set (kind of a simple inventory done). My last efforts that are still ongoing (cough) are splitting my NixOS modules off into a separate flake using flake-parts.
I do understand you meant having the stuff that your need work, I just wanted to hint that the language is very powerful and as such, most configurations have room for improvement, as in learning to do things more efficient or do things that weren’t possible before.
OhVenus_Baby@lemmy.ml 3 weeks ago
More powerful = more mental burden and capacity used to know how to run and manage its unique syntax and structure.
Sincerely NIX user daily. Switching away from nix and off to fedora kinoite.