Modular, context-aware and aspect-oriented dendritic Nix configurations. Discussions: https://oeiuwq.zulipchat.com/join/nqp26cd4kngon6mo3ncgnuap/ den.oeiuwq.com
configurations den dendritic nix aspect oriented
8
fork

Configure Feed

Select the types of activity you want to include in your feed.

Update README.md

Signed-off-by: Victor Borja <vborja@apache.org>

authored by

Victor Borja and committed by
GitHub
067282ff ec6566dc

+5 -3
+5 -3
README.md
··· 16 16 These configurations become specific when applied to your particular infra entities (hosts/users), 17 17 while allowing re-usable aspects to be shared between hosts, users, or across other flakes and non-flake projects. 18 18 19 + 20 + 19 21 <table> 20 22 <tr> 21 23 <td> ··· 64 66 </tr> 65 67 </table> 66 68 67 - Den has Zero Dependencies. The only requirement is being included in a module that has `{ config, lib, ... }` 68 - 69 - `den.lib` is domain agnostic, it can be used to configure anything Nix-configurable. 69 + Den has Zero Dependencies. `den.lib` is domain agnostic, it can be used to configure anything Nix-configurable. 70 70 71 71 On top of `den.lib`, Den also provides a [framework](https://den.oeiuwq.com/explanation/context-pipeline/) for the NixOS/nix-Darwin/Home-Manager Nix domains. 72 72 73 73 Den embraces your Nix choices and does not impose itself. All parts of Den are optional and replaceable. Works with your current setup, with/without flakes, flake-parts or any other Nix module system. 74 + 75 + > [Den is a declarative data transformation pipeline](https://github.com/vic/den/discussions/355). Infra entities are traversed via `den.ctx` transformations and configurations for them are generated when `den.aspects` are applied at each context stage. 74 76 75 77 <table> 76 78 <tr>