Post #2410179
2026-02-03 23:40 UTC
For example, in my personal flake, I created an orchestration module that maps dendritic.nixosConfigurations to flake.nixosConfigurations with some conventions and explicit features. The "dendritic" nature really lies in the default "features".
For example, I create default feature, which "collects" features from other dendrites. Elsewhere, I have a "josh" aspect which for nixos adds my user/keys and configures my home. It self-registers with the default aspect, so "josh" is on every nixos.
Replies (1)
-
@misterjoshua@fosstodon.org 2026-02-03 23:46
And "vac" is a pretty interesting case. It's a shared computer between me and my family. It has two main modes: workstation and family. These modes are represented by different nixosConfigurations. Family mode is family friendly, so an easy desktop, usual productivity tools, games, and so on. Family access also adds their users to the system. Workstation mode is josh's dev env. Docker, "weird" WM, etc. But family access lets family switch to family mode after logging in.