• 16 Posts
  • 222 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • You got some great answers already :)

    Let me just add that, in general, it’s expected to have executable files inside your home directory.

    For example, ~/.local/bin is intended for user executables and usually added to the $PATH, and a lot of package managers (such as cargo, go, pip,…) will install applications under ~ (Steam also does that).







  • Based on a US distro whose versions are supported for 1 year, and “built to the requirements for the EU public sector” (because the EU public sector has one coherent set of requirements and the dev knows them, even if he doesn’t list them out).

    This is most probably good-intentioned and it is admirable how the dev sprung into action, but it’s naive at best.










  • I too experimented with k3s, but then abandoned the idea of using it after I realized the proper way to run postgres on it was (IIUC) to use bitnami’s helm chart. I like to have some level of understanding of how my homelab and it’s config works, and that humongous amount of unreadable templates was not appealing in the least.

    As for containers, I am not really looking for service isolation (IIUC until ##368565 lands, all virtualisation.oci-containers basically run as root and I’m fine with that*)… I just want to be able to run different (usually more recent, but in nixos one also can’t easily “pin” an older version of a package if the need arises **) versions of services than those packaged is nixos. Also, not all services I want to run are available as nixos packages, and even less have modules.

    * I know what risk I’m running (more or less): nothing in my homelab is accessible from outside my lan and, even if the container host was somehow pwned, that machine can’t really do much harm (the important stuff is on a separate one).

    ** I guess I could import an older version of nixpkgs in my flake, but that requires way too much editing just to pin a package (time I’d rather spend solving the actual issue).