Skip to main content
tdro

Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

tdro micro.thedroneely.com view
  • Markdown Plaintext Embed Permalink
  • 96/50 words 32s read
    Nix/NixOS are great for documenting system configurations/models, but the long evaluation times make for slow feed back loops.

    My knowledge of the functional ecosystem is mostly diddly, but maybe there’s a way to speed it up? Ignore all module and package imports and piece together a minimal evaluation perhaps?

    nix
    { ... }:
    
    {
      imports = [
        <nixpkgs/nixos/modules/programs/git.nix>
        <nixpkgs/nixos/modules/security/auditd.nix>
        <nixpkgs/nixos/modules/services/databases/postgresql.nix>
      ];
    
      nixpkgs.overlays = [
        (_: pkgs: {
          cpio = pkgs.callPackage <nixpkgs/pkgs/tools/archivers/cpio/default.nix> { };
        })
      ];
    }

    If that goes anywhere, maybe that’s an article, but I’m fairly certain someone must have tried something like this already.

    #linux
    tdro

    Another wandering soul whispering into the void. If you are looking for my blog you are in the wrong place. The profile and header pictures are brought to you by cdd20.

    tdro micro.thedroneely.com view
  • Markdown Plaintext Embed Permalink
  • 77/50 words 26s read

    The peculiar thing about the nix ecosystem, is that the easiest way I’ve been able to convince someone to try nix is to first show nix-env. Then apply the idea of declarative package management. Not too long after that they’re on NixOS or using nix flakes, and have catapulted far past my own knowledge of nix.

    Only recently did I discover that in the wider ecosystem, using nix-env is a big no-no — that’s sort of interesting.

    #linux

    Authors

    Gallery

    Web Feeds (6)

    Web Links