Comment on How to propperly Ansible and selfhost without burning out?

• Sightline@lemmy.world ⁨1⁩ ⁨day⁩ ago

  Nix has issues, personally I’m using an immutable distro. Right now I can go upstairs and yank the power and it’ll boot right back up like nothing ever happened.

  I want something rock solid, and neither Ansible or NixOS provide that. Here’s the article that I took inspiration from: words.filippo.io/frood/

  source

  • non_burglar@lemmy.world ⁨22⁩ ⁨hours⁩ ago

    I love alpine, and I use it where I can. And it has many advantages over other distros and setups. But a declarative, ram-only distro that boots over the network doesn’t help manage non-conformant machines.

    I still need to manage Debian, old centos boxes, Ubuntu machines, and a couple old-as-time sun machines. Nixos isn’t the tool for that job. Ansible has two dependencies: ssh and python, and there are ways around the 2nd one. Ansible works really well here.

    Not trying to bash nixos, here, but I’m not sure why so many users on Lemmy compare ansible and nix, they don’t really operate in the same spaces.

    source
  • i_am_not_a_robot@discuss.tchncs.de ⁨1⁩ ⁨day⁩ ago

    An immutable distro… like NixOS? Or do you mean your root filesystem is immutable? NixOS can do that too. You could normally mount your nix store as readonly and remount rw during updates if you really care about filesystem immutability, or use some snapshot system if you’re paranoid about adding new files to the store corrupting other files already in the store during an update.

    The nixpkgs VM creation module, which I’ve never seen documentation for, has a mode where it generates a kernel, initrd, kernel command line, and erofs image containing a prepopulated /nix directory and that’s enough to boot the VM.

    Ansible is disappointing as an IAC tool. It’s good for doing things, but it’s not good for converging systems to a desired state. Too often you end up with playbooks that are not idempotent or rely on something that was done during a previous execution of the playbook or just don’t do something that was done by a previous version, and then unless you are constantly recreating your systems you won’t notice until it’s a problem and you can’t get your system back.

    source

    • Sightline@lemmy.world ⁨1⁩ ⁨day⁩ ago

      I mean my root filesystem is immutable. After trying NixOS and seeing that article I linked about an immutable NAS using Alpine I decided to try it for myself. I found it easier to just customize the Arch ISO builder and generate/update images as needed. Packages aren’t pinned and it’s not 100% deterministic, but that’s fine it’s a risk I’m willing to take.

      Also I found NixOS annoying:

      1. Because of the language

      2. Because the scripts/language (I forget the command) was doing god knows what behind the scenes. My needs aren’t that complicated I’m comfortable with just manually setting things up and locking that in by generating an Arch image.

      source