| 19 Oct 2021 |
 mars | ah OK cool | 16:40:54 |
 @kraftnix:matrix.org | * agenix is used for secretd management. https://devos.divnix.com/secrets.html | 16:41:05 |
| mars | profiles are just modules that don't define any new config options? | 16:41:06 |
| @kraftnix:matrix.org | have a read through the docs, it shoulf answer many of these questions :) | 16:41:34 |
| mars | oh God the Nixpkgs documentation uses definition the opposite of the way that I meant it | 16:43:34 |
| mars | what's the point of the conceptual distinction between suites and profiles? don't profiles that import other profiles essentially retain all the same properties as other profiles? | 16:48:58 |
 ultranix | how is deploy-rs set up to read home-manager.shared-modules | 16:50:18 |
| mars | In reply to @ultranix:matrix.org
how is deploy-rs set up to read home-manager.shared-modules deploy-rs doesn't have to do anything; it's just deploying a NixOS host flake
digga uses fup's hostDefaults.modules to add home-manager to all the host flakes | 16:54:23 |
| mars | the part where it passes the modules arg to home-manager is in fup-adapter.nix | 16:56:44 |
| mars | did i miss anything? | 17:00:11 |
| mars | what does setting
nixConfig.extra-experimental-features = "nix-command flakes ca-references";
at the top of flake.nix actually achieve? won't Nix not actually read the flake anyway, it those features are not enabled? | 17:24:24 |
| ultranix | adds hem to /etc/nix/nix.conf | 17:28:20 |
| ultranix | * adds them to /etc/nix/nix.conf | 17:28:26 |
| ultranix | flakes wont be enabled otherwise | 17:28:42 |
| mars | I guess I'm just wondering why the top-level thing is being used instead of having that live down inside a NixOS module somewhere | 17:30:40 |
| mars | if it's just a style thing, that's cool
I'm just trying to learn from the template | 17:35:33 |
| ultranix | i really liked nixus because it was 100% nix | 17:37:33 |
| mars | ok, looks like most of the interesting stuff in digga might be in its importers | 18:37:42 |
| mars | I'm a little fuzzy on the distinction between internal, external, and in-house overlays as mentioned in the source comment next to importOverlays | 18:38:28 |
| mars | looks like there's something similar going on for hosts | 18:43:03 |
| mars | feels weird that we're using import machinery in flake.nix right next to the thing fup gives us to avoid importing modules ourselves | 18:43:48 |
| mars | In reply to @mars:jupiterbroadcasting.com
ok, looks like most of the interesting stuff in digga might be in its importers which, slightly surprisingly, are also exporters!
hm | 22:28:12 |
| mars | trying to get a feel for why devos is so eager to export
I partially get it and I partially don't
like how come devos users end up exporting an output lib?
is that just for historical reasons, because folks may be using the devos repo on github as a library in their flakes rather than as a template? | 22:54:39 |
| mars | or is it just an example and it happens to give you devos' lib
like just another example of the many kinds of outputs you might want your flake to have, and a lib for other flakes to use is one of them? | 23:26:47 |
 David Arnold (blaggacao) | In reply to @mars:jupiterbroadcasting.com
what's the point of the conceptual distinction between suites and profiles? don't profiles that import other profiles essentially retain all the same properties as other profiles? Suites are host classes. It's probably most useful if you're managing a Univerity with DevOS. But behold, you can use a few suites for yourself, too, to get in the mood. Roughly, that's it. | 23:53:54 |
 tomberek | So it is an organizational distinction? No difference in the invariants? | 23:55:04 |
| David Arnold (blaggacao) | In reply to @mars:jupiterbroadcasting.com
what does setting
nixConfig.extra-experimental-features = "nix-command flakes ca-references";
at the top of flake.nix actually achieve? won't Nix not actually read the flake anyway, it those features are not enabled? Obsolete declarativeness. 😆 You can call it a fetish. | 23:55:18 |
| David Arnold (blaggacao) | In reply to @ultranix:matrix.org
i really liked nixus because it was 100% nix Deploy-rs has this long running watcher process on the target. Maybe nixus was nix + bash though? | 23:56:51 |
| David Arnold (blaggacao) | In reply to @mars:jupiterbroadcasting.com
I'm a little fuzzy on the distinction between internal, external, and in-house overlays as mentioned in the source comment next to importOverlays internal overlays don't get exposed in outputs.overlays. a way to present a nice & tidy frontyard to your neoghbours... | 23:58:11 |
| David Arnold (blaggacao) | In reply to @mars:jupiterbroadcasting.com
feels weird that we're using import machinery in flake.nix right next to the thing fup gives us to avoid importing modules ourselves Most all fup importers come out of our feathers. At some points, ecplicit importing might be a tid more declarative / explicit, without being verbose (hopefully) | 23:59:29 |
