| 3 Jun 2022 |
 Buckley | also, /dev/disk/by-id/ stays consistent across reinstalls | 03:54:46 |
 tpw_rules | also, it looks like colmena just wraps nix command line tools, there's no API or database munging | 03:55:01 |
| Buckley | no database, right | 03:55:41 |
| Buckley | and yeah it just sort of sits on top of the existing nix toolset | 03:56:27 |
| tpw_rules | what does colmena mean by "hive"? | 03:56:59 |
| Buckley | a hive is a large config containing all your server configs | 03:57:24 |
| Buckley | it can just be a single file that imports a bunch of individual server configs if that's what you like | 03:57:46 |
| Buckley | i actually have a flake with my hosts configured in the standard flakes way, and then a couple very small shims that connect that to colmena | 03:58:24 |
| tpw_rules | ahh i see | 03:58:30 |
| tpw_rules | it looks like colmena has a custom flakes output name, is that kosher-ish? | 03:58:42 |
| Buckley | like how nix flake check says that colmena is an unknown output? | 03:59:51 |
| tpw_rules | i guess | 04:00:25 |
| Buckley | you can have non-standard flake outputs, and that's fine, as long as they don't collide with any official output names in the future | 04:01:19 |
| Buckley | i doubt the official spec will ever define a colmena output, so its good by me | 04:01:50 |
| Buckley | * i doubt the official flake spec will ever define a colmena output, so its good by me | 04:01:59 |
| Buckley | the nixpkgs repo actually has a lib output which is not an official nix standard | 04:02:26 |
| tpw_rules | ah ok | 04:05:43 |
| tpw_rules | is it possible to separate a nixos machine's hostname from the thing you use in nixosConfigurations and the name of the store path? | 04:05:53 |
| tpw_rules | seems to be what system.name and system.nixos.label configuration options are for | 04:13:41 |
| Buckley | not sure, hasnt really come up | 04:15:28 |
| Buckley | outside of colmena, i believe networking.hostName sets the machine name, and you can set the nixosConfigurations.<xyz> to whatever you want | 04:17:09 |
| tpw_rules | i guess it wouldn't in a network use case | 04:17:12 |
| tpw_rules | thanks for the info though | 04:19:20 |
 Linux Hackerman | Last I checked, colmena didn't actually set the host name and forgetting it resulted in all my hosts being called nixos x) | 07:28:54 |
 dantefromhell | In reply to @buckley310:matrix.org
also, /dev/disk/by-id/ stays consistent across reinstalls if you can use GPT partition table you can label each partition.
that allows me to generalize the nix expressions for partitions.
still working on automation of the partitioning itself. | 11:19:41 |
| dantefromhell | In reply to @buckley310:matrix.org
outside of colmena, i believe networking.hostName sets the machine name, and you can set the nixosConfigurations. to whatever you want e.g. the hardware serial number... | 11:21:59 |
| 6 Jun 2022 |
|  kraem changed their profile picture. | 14:48:10 |
| Buckley | When i try to use a targetUser other than root, i get errors pushing content to servers
error: cannot add path '/nix/store/phfygaw0iga0dkdgm7qcj2rhq49viwmj-foo' because it lacks a valid signature
should not privilegeEscalationCommand be used while pushing content, as well as activating it, or is there a reason for this? | 16:08:42 |
| Linux Hackerman | Buckley: I guess it would work if the user were in Nix's trusted-users | 22:48:47 |
| Linux Hackerman | So it's not strictly necessary | 22:49:08 |
