| 19 Aug 2023 |
 Wanja Hentze | it all builds on the deploying host, not the deployed host | 16:22:46 |
| Wanja Hentze | which is a beefy CI machine in this case | 16:23:07 |
| Wanja Hentze | maybe you're confused because you're used to running nixos-rebuild on the hosts | 16:26:04 |
| Wanja Hentze | colmena by default builds locally and then pushes to the remote hosts | 16:26:17 |
| Wanja Hentze | so in that sense you're automatically sharing built things as long as you're deploying several hosts from the same local host | 16:26:42 |
 @khalilsantana:matrix.org | But I mean, say if I add some new package to my config.nix, that will be built locally (deployment machine) and then the artefacts copied to the remote targets. But can I somehow fetch whatever package upgrades needed for existing hosts, build them once and share them across hosts using colmena (I seems like no?) | 19:16:04 |
| Wanja Hentze | (I don't understand the question but maybe somebody else does) | 19:21:37 |
 Zhaofeng Li | In reply to @khalilsantana:matrix.org
But I mean, say if I add some new package to my config.nix, that will be built locally (deployment machine) and then the artefacts copied to the remote targets. But can I somehow fetch whatever package upgrades needed for existing hosts, build them once and share them across hosts using colmena (I seems like no?) This is what currently happens. When you deploy a new config, Colmena won't copy paths that already exist on the remote host. | 19:24:38 |
| Zhaofeng Li | For example, you edit networking.hostName, the new system profile closure is mostly identical to the old one except for a few paths | 19:25:59 |
