about summary refs log tree commit diff
path: root/nixos/doc/manual/from_md/configuration/profiles.chapter.xml
blob: 6f5fc130c6a07ccdaad1adc1c5a2a70482fc10c5 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<chapter xmlns="http://docbook.org/ns/docbook"  xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="ch-profiles">
  <title>Profiles</title>
  <para>
    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
    <literal>&lt;nixpkgs/nixos/modules/profiles&gt;</literal>. That is
    to say, expected usage is to add them to the imports list of your
    <literal>/etc/configuration.nix</literal> as such:
  </para>
  <programlisting language="bash">
imports = [
  &lt;nixpkgs/nixos/modules/profiles/profile-name.nix&gt;
];
</programlisting>
  <para>
    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.
  </para>
  <para>
    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.
  </para>
  <xi:include href="profiles/all-hardware.section.xml" />
  <xi:include href="profiles/base.section.xml" />
  <xi:include href="profiles/clone-config.section.xml" />
  <xi:include href="profiles/demo.section.xml" />
  <xi:include href="profiles/docker-container.section.xml" />
  <xi:include href="profiles/graphical.section.xml" />
  <xi:include href="profiles/hardened.section.xml" />
  <xi:include href="profiles/headless.section.xml" />
  <xi:include href="profiles/installation-device.section.xml" />
  <xi:include href="profiles/minimal.section.xml" />
  <xi:include href="profiles/qemu-guest.section.xml" />
</chapter>