Push builds to bigbox2 over ssh-ng from a background queue
bigbox2 runs nix-serve, which only serves its own store: every 'nix copy --to http://bigbox2.lab.internal:5000' from the post-build hook ended in HTTP 404 after compressing the whole closure, so nothing ever landed and the next build tried the same paths again. A post-build-hook also blocks the build until it returns, which held up every build on fwdesk (nbot's VM checks spent most of a cold CI run there). - cacheReceive (on bigbox2): nix.sshServe with write over ssh-ng, for fwdesk's ssh host key; nix-ssh is trusted, and nix-serve signs the pushed paths when it serves them. - cachePush: the hook only queues $OUT_PATHS. nix-cache-push.service drains the queue with nix copy to ssh-ng://nix-ssh@bigbox2.lab.internal as the host key, with bigbox2's host key pinned; a path unit starts it, and a failed push is retried every 10 minutes by a timer. Co-Authored-By: nBot
This commit is contained in:
1 parent
6db82ed10a
commit
10d85b2a91
2 files changed
+117
-21
No files matched your search
@@ -20,6 +20,8 @@
|
||||
parent = "enp3s0";
|
||||
};
|
||||
cachePush.enable = false;
|
||||
# fwdesk pushes its builds here over ssh-ng; nix-serve serves them.
|
||||
cacheReceive.enable = true;
|
||||
};
|
||||
|
||||
networkDrives = {
|
||||
|
||||
Reference in new issue
Block a user