1229e735ac
this adds support for structural includes to nixos-render-docs. structural includes provide a way to denote the (sub)structure of the nixos manual in the markdown source files, very similar to how we used literal docbook blocks before, and are processed by nixos-render-docs without involvement of xml tooling. this will ultimately allow us to emit the nixos manual in other formats as well, e.g. html, without going through docbook at all. alternatives to this source layout were also considered: a parallel structure using e.g. toml files that describe the document tree and links to each part is possible, but much more complicated to implement than the solution chosen here and makes it harder to follow which files have what substructure. it also makes it much harder to include a substructure in the middle of a file. much the same goes for command-line arguments to the converter, only that command-lined arguments are even harder to specify correctly and cannot be reasonably pulled together from many places without involving another layer of tooling. cli arguments would also mean that the manual structure would be fixed in default.nix, which is also not ideal.
34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
# Profiles {#ch-profiles}
|
|
|
|
In some cases, it may be desirable to take advantage of commonly-used,
|
|
predefined configurations provided by nixpkgs, but different from those
|
|
that come as default. This is a role fulfilled by NixOS's Profiles,
|
|
which come as files living in `<nixpkgs/nixos/modules/profiles>`. That
|
|
is to say, expected usage is to add them to the imports list of your
|
|
`/etc/configuration.nix` as such:
|
|
|
|
```nix
|
|
imports = [
|
|
<nixpkgs/nixos/modules/profiles/profile-name.nix>
|
|
];
|
|
```
|
|
|
|
Even if some of these profiles seem only useful in the context of
|
|
install media, many are actually intended to be used in real installs.
|
|
|
|
What follows is a brief explanation on the purpose and use-case for each
|
|
profile. Detailing each option configured by each one is out of scope.
|
|
|
|
```{=include=} sections
|
|
profiles/all-hardware.section.md
|
|
profiles/base.section.md
|
|
profiles/clone-config.section.md
|
|
profiles/demo.section.md
|
|
profiles/docker-container.section.md
|
|
profiles/graphical.section.md
|
|
profiles/hardened.section.md
|
|
profiles/headless.section.md
|
|
profiles/installation-device.section.md
|
|
profiles/minimal.section.md
|
|
profiles/qemu-guest.section.md
|
|
```
|