summary refs log tree commit diff
path: root/nixos/doc/manual/configuration/profiles.xml
blob: 9d08f7f7bed2f564ed55e37f8f8776f742423003 (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
39
<chapter xmlns="http://docbook.org/ns/docbook"
         xmlns:xlink="http://www.w3.org/1999/xlink"
         xmlns:xi="http://www.w3.org/2001/XInclude"
         version="5.0"
         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 <filename>&lt;nixpkgs/nixos/modules/profiles&gt;</filename>.
  That is to say, expected usage is to add them to the imports list of your
  <filename>/etc/configuration.nix</filename> as such:
 </para>
<programlisting>
  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.xml" />
 <xi:include href="profiles/base.xml" />
 <xi:include href="profiles/clone-config.xml" />
 <xi:include href="profiles/demo.xml" />
 <xi:include href="profiles/docker-container.xml" />
 <xi:include href="profiles/graphical.xml" />
 <xi:include href="profiles/hardened.xml" />
 <xi:include href="profiles/headless.xml" />
 <xi:include href="profiles/installation-device.xml" />
 <xi:include href="profiles/minimal.xml" />
 <xi:include href="profiles/qemu-guest.xml" />
</chapter>