Post #388723
2026-02-03 23:23 UTC
I think I'm finally "getting it" for dendritic nix flake designs. The big moments for me were:
1. Starting to think in terms of features and the contexts where those features apply. When coding, "features" map directly to flake.module aspects and contexts map directly to flake.module classes.
2. Realizing that you build an orchestration mechanism to pull your features together by convention or explicit reference. The orchestration could be a function or a flake-context module.
Replies (1)
-
@misterjoshua@fosstodon.org 2026-02-03 23:40
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.