Subnostr

#asknostr I gave up on #NixOS, it didn't want to work the way I had wanted it to. So, now I need an alternative. Are there systems like NixOS - or something similiar - where you have one config file to define but the whole and entire OS?

Use Cases:

- Define my btcd and cln config/plugins install additional software and make those services all go through Tor.

- Define my k3s node; Node config and friends and have basically nothing else on it aside from Telegraf for whole-system-monitoring.

Sadly, OpenWrt isn't really fit for this; although it's uci config system is amazing! But it only does configs, not packages, so this is a little difficult...

Long term, I want to store those host configs in git a-la `$hostname/...files...` and perhaps `shared/` to in case some things can in fact be shared like k8s deployments. o.o

59f8fccf... 1y ago

nostr:npub1tcekjparmkju6k83r5tzmzjvjwy0nnajlrwyk35us9g7x7wx80ys9hjmky What was it about NixOS that you didn't like?

Maybe buildroot/yocto/some other embedded distro will do what you want?

Reply to this note

Please Login to reply.

Discussion

Ingwie Phoenix (aka. birb) 1y ago

My biggest problem was that I couldn't figure out what the stack traces were saying. In my case, attempting to import nix-bitcoin always resulted in cyclic, infinite imports - however, I had no idea what exactly caused it, and the trace wouldn't tell me.

Plus, each time you do run a nix command, the entire stack of files from all sources is evaluated - meaning, it is insanely slow. Honestly I am surprised they haven't switched to a partially precomputed model yet... Because it is so, _so_ slow. It gets better on bigger hardware, like amd64 CPUs, but I was trying to deploy in an aarch64 LXC/incus container - and it was awful.

I tried to debug this and to get it working, but I couldn't get anywhere. So now I am looking at terraform/opentofu and other automations to just spin up an lxc container with Alpine instead and just deploy into that.

Frustrating...