| 28 Nov 2024 |
 ElvishJerricco | * You can avoid re-evaluating by setting pkgs in the nixosSystem call, I believe. Or by setting the nixpkgs.pkgs nixos option. Either of these will break anything in the nixpkgs.* nixos options (though I think that module yells at you about that now so it'll be obvious) | 13:40:16 |
| ElvishJerricco | that said, I'm not even sure nixpkgs eval is the slowest part tbh. NixOS module evaluation might be worse, and you're not going to get that to be shared | 13:41:15 |
 Leonardo Santiago | In reply to @elvishjerricco:matrix.org
that said, I'm not even sure nixpkgs eval is the slowest part tbh. NixOS module evaluation might be worse, and you're not going to get that to be shared I imagined it, which is sad. the design is pretty modular, as in, it should be able to evaluate the modules separately and then just re-use them for all configs. I was wondering if there was a way to restructure my code to do it like that. | 13:53:08 |
| ElvishJerricco | I mean that's not really possible | 13:53:36 |
| Leonardo Santiago | but I don't know enough about the internals of nix flake check for that | 13:53:37 |
| ElvishJerricco | any module can affect any other module arbitrarily | 13:53:43 |
| ElvishJerricco | so if two configs aren't literally exactly identical (I mean exactly) then there's basically zero potential for sharing | 13:54:20 |
| Leonardo Santiago | that is fair, I didn't think about that | 13:54:23 |
| ElvishJerricco | Leonardo Santiago: I'd give it a try to reduce the nixpkgs instantiations by setting them all to the same pkgs and see how much that helps | 13:55:21 |
| Leonardo Santiago | I'll try doing that | 13:56:24 |
| Leonardo Santiago | I'm also experimenting with nix-eval-jobs --flake .#nixosConfigurations but it doesn't seem to do what I want? it either returns instantaneously with no output or enters an infinite loop with --force-recurse | 13:57:23 |
| Leonardo Santiago | not sure I'm using it correctly | 13:57:30 |
| ElvishJerricco | Leonardo Santiago: You probably need to specify the exact toplevel attributes, not just nixosConfigurations | 15:05:26 |
| ElvishJerricco | i.e. I'd create an output attribute like toplevels = mapAttrs (_: cfg: cfg.system.build.toplevel) self.nixosConfigurations; and eval that | 15:06:34 |
| Leonardo Santiago | what does that mean? I'd like for it to evaluate each nixosConfiguration under that in it's own thread. how would I do it? spell out each attr I'd like it to eval in there? | 15:06:35 |
 adamcstephens | it means you can't eval nixosConfigurations.name . Try and do so with nix eval .#nixosConfigurations.name and you'll see it won't work | 16:01:40 |
| adamcstephens | but you can evaluate the system toplevel.
❯ nix eval .#nixosConfigurations.nest1.config.system.build.toplevel
«derivation /nix/store/6yc0q5y7wyladjg0y8wlkxla88rli1lb-nixos-system-nest1-24.11.20241116.057f63b.drv»
| 16:02:02 |
| adamcstephens | elvish was suggesting you create another attribute that maps your nixos configs into that you can then pass to nix-eval-jobs | 16:03:17 |
| adamcstephens | anyone have a tool they like to use for inspecting tls certificates locally or remotely, that isn't openssl (i know how to use it, i don't want to ) | 16:21:48 |
 hexa | no | 16:25:43 |
 Morgan | locally, keystore-explorer isn't awful | 16:36:18 |
| Morgan | there are a lot of not so good options in general though | 16:36:46 |
| Morgan | https://lapo.it/asn1js/ | 16:39:47 |
| Morgan | isn't bad, provides interactive hexdumps | 16:39:57 |
| adamcstephens | sorry, i should have clarified i want a CLI tool | 16:45:27 |
| Morgan | ah, yeah, neither of those are that. 😩 | 17:31:38 |
| Morgan | give https://search.nixos.org/packages?channel=24.05&show=certigo&from=0&size=50&sort=relevance&type=packages&query=Certigo a try | 17:33:48 |
| Morgan | I think that one can output json too | 17:34:42 |
| adamcstephens | 
Download ima_96a97f1.jpeg | 18:34:51 |
| adamcstephens | Just got an email from hetzner on their US cloud offering. More expensive and significantly less traffic | 18:34:52 |
