| 17 Jul 2022 |
 Winter (she/her) | which stanza? | 05:58:56 |
 rendakuenthusiast | the one with the vhost I was trying to get rid of | 07:24:44 |
|  Christos Trochalakis joined the room. | 07:49:05 |
| Christos Trochalakis | Hello! I am using colmena with flakes, is it possible to build node configurations with hydra (hydraJobs)? | 13:49:19 |
|  wiredhikari left the room. | 15:12:28 |
 Zhaofeng Li | In reply to @ctrochalakis:matrix.org
Hello! I am using colmena with flakes, is it possible to build node configurations with hydra (hydraJobs)? You may be able to wrap the node configurations back into nixosSystems. The Colmena flake exposes the deploymentOptions NixOS module so the deployment.* options still work. | 19:49:35 |
|  slby joined the room. | 20:08:22 |
| 18 Jul 2022 |
| rendakuenthusiast | another weird issue I'm running into | 04:55:45 |
| rendakuenthusiast | I wrote a helper function that woudl generate an nginx vhost set of the form { services.nginx.virtualHosts."hostname.example.com" = <nginx configuration> } | 04:56:34 |
| rendakuenthusiast | so that I could define the vhost for a service in the same module I define the service in | 04:56:58 |
| rendakuenthusiast | so I have my helper function return the above set, and then use \\ helperFunction { hostname="hostname"; } to merge it into the config set that was already being returned for each service I'm running | 04:57:32 |
| rendakuenthusiast | and this is causing existing configuration to stop appearing in ways I don't understand | 04:57:52 |
| rendakuenthusiast | if I have a set a and a set b with no keys in common, a \\ b will just merge them without overwriting anything, right? | 04:58:12 |
