┃  # Submit build to pynixd
┃
┃  $ timeout 60 nix build --file ~/Code/pynixd/tests/nix simple --store /tmp/pynixd-stores/pynixkube --max-jobs 0 --builders "ssh-ng://nix@204.168.233.183:2222 x86_64-linux - 10" 2>&1
┃
┃  this derivation will be built:
┃    /nix/store/lsbmv7xvx6qrzqvc7lim5gj5kzgxg5vk-test-1777325199.drv
┃  these 50 paths will be fetched (21.7 MiB download, 104.4 MiB unpacked):
┃    /nix/store/742ik41xpll83mwfvmrlcv5h0cfd929n-ShellCheck-0.11.0
┃    /nix/store/4sabfgpxkbv6w3mvk0wil50vdi37m9r8-acl-2.3.2
┃    /nix/store/p2yk6q3bhcz1d0wlmk907ysj4l95ak7y-attr-2.5.2
┃    /nix/store/v8sa6r6q037ihghxfbwzjj4p59v2x0pv-bash-5.3p9
┃    /nix/store/91nr5z1cwr1qch2wl58dppl02zrnlza3-brotli-1.2.0-lib
┃    /nix/store/vi21p90v3kj509rx00r101xcqa6za76b-bzip2-1.0.8
┃    /nix/store/by6npbc13ly5a1zgsqghv7wv5bklyiny-bzip2-1.0.8-bin
┃  …
┃
┃  Click to expand
┃
Build succeeded end-to-end. Let me verify the full flow in the pynixd logs:
┃
┃  # Check full build flow in logs
┃
┃  $ stern -n nixkube pynixd-0 --no-follow --color never 2>/dev/null | grep -E "dynamic_features|builder_registered|builder_job_created|build_completed|adding_store_dynamically" | tail -10
┃
┃  pynixd-0 pynixd {"features": {"x86_64-linux": "{'nixos-test', 'big-parallel', 'benchmark'}"}, "event": "dynamic_features_registered", "timestamp": "2026-04-27T21:25:31.774396Z"}
┃  pynixd-0 pynixd {"job": "nixkube-builder-aafebb9f", "event": "builder_job_created", "timestamp": "2026-04-27T21:26:46.929259Z"}
┃  pynixd-0 pynixd {"store_id": "builder-nixkube-builder-aafebb9f-hk6zq", "dynamic": true, "event": "adding_store_dynamically", "timestamp": "2026-04-27T21:27:22.888235Z"}
┃  pynixd-0 pynixd {"store_id": "builder-nixkube-builder-aafebb9f-hk6zq", "pod_ip": "10.133.1.108", "event": "builder_registered", "timestamp": "2026-04-27T21:27:22.888318Z"}
┃  pynixd-0 pynixd {"build_id": 1, "event": "build_completed", "timestamp": "2026-04-27T21:27:33.141571Z"}
┃
▣  Build · glm-5.1

Man this has been a long time in the making 🤣 pynixd running in Kubernetes and creating backends dynamically, end-to-end. (The Kubernetes logic is really shit)

┃  # Submit build to pynixd
┃
┃  $ timeout 60 nix build --file ~/Code/pynixd/tests/nix simple --store /tmp/pynixd-stores/pynixkube --max-jobs 0 --builders "ssh-ng://nix@204.168.233.183:2222 x86_64-linux - 10" 2>&1
┃
┃  this derivation will be built:
┃    /nix/store/lsbmv7xvx6qrzqvc7lim5gj5kzgxg5vk-test-1777325199.drv
┃  these 50 paths will be fetched (21.7 MiB download, 104.4 MiB unpacked):
┃    /nix/store/742ik41xpll83mwfvmrlcv5h0cfd929n-ShellCheck-0.11.0
┃    /nix/store/4sabfgpxkbv6w3mvk0wil50vdi37m9r8-acl-2.3.2
┃    /nix/store/p2yk6q3bhcz1d0wlmk907ysj4l95ak7y-attr-2.5.2
┃    /nix/store/v8sa6r6q037ihghxfbwzjj4p59v2x0pv-bash-5.3p9
┃    /nix/store/91nr5z1cwr1qch2wl58dppl02zrnlza3-brotli-1.2.0-lib
┃    /nix/store/vi21p90v3kj509rx00r101xcqa6za76b-bzip2-1.0.8
┃    /nix/store/by6npbc13ly5a1zgsqghv7wv5bklyiny-bzip2-1.0.8-bin
┃  …
┃
┃  Click to expand
┃
Build succeeded end-to-end. Let me verify the full flow in the pynixd logs:
┃
┃  # Check full build flow in logs
┃
┃  $ stern -n nixkube pynixd-0 --no-follow --color never 2>/dev/null | grep -E "dynamic_features|builder_registered|builder_job_created|build_completed|adding_store_dynamically" | tail -10
┃
┃  pynixd-0 pynixd {"features": {"x86_64-linux": "{'nixos-test', 'big-parallel', 'benchmark'}"}, "event": "dynamic_features_registered", "timestamp": "2026-04-27T21:25:31.774396Z"}
┃  pynixd-0 pynixd {"job": "nixkube-builder-aafebb9f", "event": "builder_job_created", "timestamp": "2026-04-27T21:26:46.929259Z"}
┃  pynixd-0 pynixd {"store_id": "builder-nixkube-builder-aafebb9f-hk6zq", "dynamic": true, "event": "adding_store_dynamically", "timestamp": "2026-04-27T21:27:22.888235Z"}
┃  pynixd-0 pynixd {"store_id": "builder-nixkube-builder-aafebb9f-hk6zq", "pod_ip": "10.133.1.108", "event": "builder_registered", "timestamp": "2026-04-27T21:27:22.888318Z"}
┃  pynixd-0 pynixd {"build_id": 1, "event": "build_completed", "timestamp": "2026-04-27T21:27:33.141571Z"}
┃
▣  Build · glm-5.1

Man this has been a long time in the making 🤣 pynixd running in Kubernetes and creating backends dynamically, end-to-end functionality!!!!! (The Kubernetes logic is really shit)

{ lib
, ...
}:
# $FLAKE should be configured to where your repository is located
# Preferably using direnv, you can also set it into your sessionVariables
let
  dot_path = "${builtins.getEnv("FLAKE")}/sub/dir/";
  dot_paths = lib.filesystem.listFilesRecursive dot_path;
  dot_strings = builtins.map (x: builtins.toString x) dot_paths;
  dot_prefixDeleted = builtins.map (x: builtins.replaceStrings [ dot_path ] [ "" ] x) dot_strings;
  dotfile_outOfStoreLinked = lib.attrsets.genAttrs dot_prefixDeleted (name: {
    source = config.lib.file.mkOutOfStoreSymlink (dot_path + name);
  });
in
{
  home.file = dotfile_outOfStoreLinked;
}

I know I mentioned linking things from $FLAKE repo into $HOME which I'm quite happy with. This is the implementation I'm using. It'll replicate a tree subdir into $HOME for you, nothing using home.file.x.recursive so you won't get collisions with folders and stuff 😄

In reply to @igorramazanov:matrix.org
Would be nice to have an additional option: "does not really matter" and also allow multichoice