| 19 Jun 2023 |
 rendakuenthusiast | thanks for your help! | 06:04:29 |
| 22 Jun 2023 |
|  @h4636oh:matrix.org joined the room. | 02:47:16 |
| @h4636oh:matrix.org left the room. | 03:37:55 |
|  kenji joined the room. | 05:55:29 |
 @palo:xaos.space | I'm sketching an Architecture for a service in an openstack cluster, which consists of multiple machines (and there will be new machines every now and than). I would like to have one machine that shares it's /nix/store with all the other instanzes in the cluster. That is not a problem. I have a mono repository and would like to build all machines (not deploy) and nix-copy-closure the resulting closures to this machine. Meaning the build server (which is not the cache server) is in a loop while true; git pull ; colmena build ; nix-copy-closure ???? private_cache_server How to find all closures that need to be copied? | 08:12:45 |
 Wanja Hentze | would you even be using colmena then? sounds more like you'd be reimplementing it | 08:14:48 |
| @palo:xaos.space | I want to use colmena. Because we would not deploy all machines instantly. | 08:15:40 |
| @palo:xaos.space | I just want to enrich the cache. | 08:16:07 |
| Wanja Hentze | oh, cache warming | 08:16:37 |
| @palo:xaos.space | All machines have a very similar base setup, and updates should be pulled from the cache, to avoid uploading 50 times the same closures from my office to the data center. | 08:18:00 |
| Wanja Hentze | then why not use `colmena apply push` | 08:18:07 |
| @palo:xaos.space | In reply to @palo:xaos.space
All machines have a very similar base setup, and updates should be pulled from the cache, to avoid uploading 50 times the same closures from my office to the data center. (I answered before you asked :D) | 08:20:52 |
| @palo:xaos.space | The only solution I found so far is, a cache server that also creates the builds. | 08:21:33 |
