forked from mirrors/nixpkgs
39 lines
1.7 KiB
XML
39 lines
1.7 KiB
XML
|
<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><nixpkgs/nixos/modules/profiles></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 = [
|
||
|
<nixpkgs/nixos/modules/profiles/profile-name.nix>
|
||
|
];
|
||
|
</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>
|