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
Update README.md
Signed-off-by: Victor Borja <vborja@apache.org>
authored by
Victor Borja
and committed by
GitHub
415102e6
e61b4c3c
+32
-15
+32
-15
README.md
+32
-15
README.md
···
54
54
55
55
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.
56
56
57
-
---
58
-
59
-
### Versioning - Den `v0.x` is moving rapidly
60
-
61
-
`main` branch follows development, this is where PRs are merged, it is stable in the sense
62
-
that every PR checks CI. However, some PR might introduce changes that require you
63
-
reading the release notes. For people tracking development, we have announcements
64
-
tagged `heads-up` whenever this happens.
65
-
66
-
`latest` tag always follows the latest created tag. This is intended for people that wishes
67
-
to wait for a release and reading all announcements at release notes. if you flake update, you
68
-
will only move between release points.
69
-
70
-
Den `main` always requires flake-aspects `main`. Same for `latest` versions.
71
-
72
57
### Templates:
73
58
74
59
[default](https://den.oeiuwq.com/tutorials/default/): +flake-file +flake-parts +home-manager
···
126
111
127
112
> Den is a playground for some very advanced concepts. I’m convinced that some of its ideas will play a role in future Nix areas. In my opinion there are some raw diamonds in Den.\
128
113
> — `@Doc-Steve` - Author of [Dendritic Design Guide](https://github.com/Doc-Steve/dendritic-design-with-flake-parts)
114
+
115
+
## Den Versioning - `v0.x` is moving fast
116
+
117
+
Den `main` always requires flake-aspects `main`. Same for `latest` versions.
118
+
119
+
120
+
```nix
121
+
# Bleeding edge Den
122
+
{
123
+
inputs.den.url = "github:vic/den";
124
+
inputs.flake-aspects.url = "github:vic/flake-aspects";
125
+
}
126
+
```
127
+
128
+
`main` branch follows development, this is where PRs are merged, it is stable in the sense
129
+
that every PR checks CI. However, some PR might introduce changes that require you being
130
+
aware of what is happening in Den. For people tracking development, we have announcements
131
+
tagged `heads-up` whenever this happens.
132
+
133
+
134
+
```nix
135
+
# Released Den - no longer gets updates until next release
136
+
{
137
+
inputs.den.url = "github:vic/den/latest";
138
+
inputs.flake-aspects.url = "github:vic/flake-aspects/latest";
139
+
}
140
+
```
141
+
142
+
`latest` tag always follows the latest created tag. This is intended for people that wishes
143
+
to wait for a release and reading all announcements at release notes. if you flake update, you
144
+
will only move between release points.
145
+
129
146
130
147
## Code example (OS configuration domain)
131
148