nixos docs: give IDs to things

Changed files
+54 -54
nixos
doc
modules
i18n
input-method
programs
security
services
databases
editors
misc
taskserver
monitoring
prometheus
networking
web-apps
+1 -1
nixos/doc/manual/manual.xml
···
<subtitle>Version <xi:include href="./generated/version" parse="text" />
</subtitle>
</info>
-
<preface>
+
<preface xml:id="preface">
<title>Preface</title>
<para>
This manual describes how to install, use and extend NixOS, a Linux
+1 -1
nixos/doc/manual/options-to-docbook.xsl
···
<xsl:template match="/expr/list">
-
<appendix>
+
<appendix xml:id="appendix-configuration-options">
<title>Configuration Options</title>
<variablelist xml:id="configuration-variable-list">
<xsl:for-each select="attrs">
+4 -4
nixos/modules/i18n/input-method/default.xml
···
bridge.</para></listitem>
</itemizedlist>
-
<section><title>IBus</title>
+
<section xml:id="module-services-input-methods-ibus"><title>IBus</title>
<para>IBus is an Intelligent Input Bus. It provides full featured and user
friendly input method user interface.</para>
···
</simplesect>
</section>
-
<section><title>Fcitx</title>
+
<section xml:id="module-services-input-methods-fcitx"><title>Fcitx</title>
<para>Fcitx is an input method framework with extension support. It has three
built-in Input Method Engine, Pinyin, QuWei and Table-based input
···
</itemizedlist>
</section>
-
<section><title>Nabi</title>
+
<section xml:id="module-services-input-methods-nabi"><title>Nabi</title>
<para>Nabi is an easy to use Korean X input method. It allows you to enter
phonetic Korean characters (hangul) and pictographic Korean characters
···
</programlisting>
</section>
-
<section><title>Uim</title>
+
<section xml:id="module-services-input-methods-uim"><title>Uim</title>
<para>Uim (short for "universal input method") is a multilingual input method
framework. Applications can use it through so-called bridges.</para>
+4 -4
nixos/modules/programs/zsh/oh-my-zsh.xml
···
to manage your <link xlink:href="https://www.zsh.org/">ZSH</link> configuration
including completion scripts for several CLI tools or custom prompt themes.</para>
-
<section><title>Basic usage</title>
+
<section xml:id="module-programs-oh-my-zsh-usage"><title>Basic usage</title>
<para>The module uses the <literal>oh-my-zsh</literal> package with all available features. The
initial setup using Nix expressions is fairly similar to the configuration format
of <literal>oh-my-zsh</literal>.
···
configuration and writes it into your <literal>/etc/zshrc</literal>.
</para></section>
-
<section><title>Custom additions</title>
+
<section xml:id="module-programs-oh-my-zsh-additions"><title>Custom additions</title>
<para>Sometimes third-party or custom scripts such as a modified theme may be needed.
<literal>oh-my-zsh</literal> provides the
···
</programlisting>
</para></section>
-
<section><title>Custom environments</title>
+
<section xml:id="module-programs-oh-my-zsh-environments"><title>Custom environments</title>
<para>There are several extensions for <literal>oh-my-zsh</literal> packaged in <literal>nixpkgs</literal>.
One of them is <link xlink:href="https://github.com/spwhitt/nix-zsh-completions">nix-zsh-completions</link>
···
will be thrown if both <literal>custom</literal> and <literal>customPkgs</literal> are set.</emphasis>
</para></section>
-
<section><title>Package your own customizations</title>
+
<section xml:id="module-programs-oh-my-zsh-packaging-customizations"><title>Package your own customizations</title>
<para>If third-party customizations (e.g. new themes) are supposed to be added to <literal>oh-my-zsh</literal>
there are several pitfalls to keep in mind:</para>
+3 -3
nixos/modules/security/acme.xml
···
implemented by and for Let's Encrypt. The alternative ACME client
<literal>simp_le</literal> is used under the hood.</para>
-
<section><title>Prerequisites</title>
+
<section xml:id="module-security-acme-prerequisites"><title>Prerequisites</title>
<para>You need to have a running HTTP server for verification. The server must
have a webroot defined that can serve
···
</section>
-
<section><title>Configuring</title>
+
<section xml:id="module-security-acme-configuring"><title>Configuring</title>
<para>To enable ACME certificate retrieval &amp; renewal for a certificate for
<literal>foo.example.com</literal>, add the following in your
···
</section>
-
<section><title>Using ACME certificates in Nginx</title>
+
<section xml:id="module-security-acme-nginx"><title>Using ACME certificates in Nginx</title>
<para>NixOS supports fetching ACME certificates for you by setting
<literal><link linkend="opt-services.nginx.virtualHosts._name_.enableACME">enableACME</link> = true;</literal> in a virtualHost config. We
first create self-signed placeholder certificates in place of the
+9 -9
nixos/modules/services/databases/foundationdb.xml
···
<para>FoundationDB (or "FDB") is an open source, distributed, transactional
key-value store.</para>
-
<section><title>Configuring and basic setup</title>
+
<section xml:id="module-services-foundationdb-configuring"><title>Configuring and basic setup</title>
<para>To enable FoundationDB, add the following to your
<filename>configuration.nix</filename>:
···
</section>
-
<section><title>Scaling processes and backup agents</title>
+
<section xml:id="module-services-foundationdb-scaling"><title>Scaling processes and backup agents</title>
<para>Scaling the number of server processes is quite easy; simply specify
<option>services.foundationdb.serverProcesses</option> to be the number of
···
</section>
-
<section><title>Clustering</title>
+
<section xml:id="module-services-foundationdb-clustering"><title>Clustering</title>
<para>FoundationDB on NixOS works similarly to other Linux systems, so this
section will be brief. Please refer to the full FoundationDB documentation for
···
</section>
-
<section><title>Client connectivity</title>
+
<section xml:id="module-services-foundationdb-connectivity"><title>Client connectivity</title>
<para>By default, all clients must use the current
<command>fdb.cluster</command> file to access a given FoundationDB cluster.
···
</section>
-
<section><title>Client authorization and TLS</title>
+
<section xml:id="module-services-foundationdb-authorization"><title>Client authorization and TLS</title>
<para>By default, any user who can connect to a FoundationDB process with the
correct cluster configuration can access anything. FoundationDB uses a
···
</section>
-
<section><title>Backups and Disaster Recovery</title>
+
<section xml:id="module-services-foundationdb-disaster-recovery"><title>Backups and Disaster Recovery</title>
<para>The usual rules for doing FoundationDB backups apply on NixOS as written
in the FoundationDB manual. However, one important difference is the security
···
</section>
-
<section><title>Known limitations</title>
+
<section xml:id="module-services-foundationdb-limitations"><title>Known limitations</title>
<para>The FoundationDB setup for NixOS should currently be considered beta.
FoundationDB is not new software, but the NixOS compilation and integration has
···
</section>
-
<section><title>Options</title>
+
<section xml:id="module-services-foundationdb-options"><title>Options</title>
<para>NixOS's FoundationDB module allows you to configure all of the most
relevant configuration options for <command>fdbmonitor</command>, matching it
···
</section>
-
<section><title>Full documentation</title>
+
<section xml:id="module-services-foundationdb-full-docs"><title>Full documentation</title>
<para>FoundationDB is a complex piece of software, and requires careful
administration to properly use. Full documentation for administration can be
+3 -3
nixos/modules/services/databases/postgresql.xml
···
<para>PostgreSQL is an advanced, free relational database.<!-- MORE --></para>
-
<section><title>Configuring</title>
+
<section xml:id="module-services-postgres-configuring"><title>Configuring</title>
<para>To enable PostgreSQL, add the following to your
<filename>configuration.nix</filename>:
···
</section>
-
<section><title>Upgrading</title>
+
<section xml:id="module-services-postgres-upgrading"><title>Upgrading</title>
<para>FIXME: document dump/upgrade/load cycle.</para>
</section>
-
<section><title>Options</title>
+
<section xml:id="module-services-postgres-options"><title>Options</title>
<para>A complete list of options for the PostgreSQL module may be found <link linkend="opt-services.postgresql.enable">here</link>.</para>
+12 -12
nixos/modules/services/editors/emacs.xml
···
starting the Emacs daemon.
</para>
-
<section>
+
<section xml:id="module-services-emacs-installing">
<title>Installing <application>Emacs</application></title>
<para>
···
can be enabled.
</para>
-
<section>
+
<section xml:id="module-services-emacs-releases">
<title>The Different Releases of Emacs</title>
<para>
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-emacs-adding-packages">
<title>Adding Packages to Emacs</title>
<para>
Emacs includes an entire ecosystem of functionality beyond
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-emacs-advanced">
<title>Advanced Emacs Configuration</title>
<para>
···
</section>
</section>
-
<section>
+
<section xml:id="module-services-emacs-running">
<title>Running Emacs as a Service</title>
<para>
<productname>NixOS</productname> provides an optional
···
<filename>modules/services/editors/emacs.nix</filename>
</para>
-
<section>
+
<section xml:id="module-services-emacs-enabling">
<title>Enabling the Service</title>
<para>
···
</section>
-
<section>
+
<section xml:id="module-services-emacs-starting-client">
<title>Starting the client</title>
<para>
Ensure that the emacs server is enabled, either by customizing
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-emacs-editor-variable">
<title>Configuring the <varname>EDITOR</varname> variable</title>
<!--<title><command>emacsclient</command> as the Default Editor</title>-->
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-emacs-per-user">
<title>Per-User Enabling of the Service</title>
<para>
···
</section>
</section>
-
<section>
+
<section xml:id="module-services-emacs-configuring">
<title>Configuring Emacs</title>
<para>
···
server-switch-hook, server-done-hook?
-->
-
<section>
+
<section xml:id="module-services-emacs-major-mode">
<title>A Major Mode for Nix Expressions</title>
<para>
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-emacs-man-pages">
<title>Accessing man pages</title>
<para>
You can use <function>woman</function> to get completion of all
+3 -3
nixos/modules/services/misc/gitlab.xml
···
<para>Gitlab is a feature-rich git hosting service.</para>
-
<section><title>Prerequisites</title>
+
<section xml:id="module-services-gitlab-prerequisites"><title>Prerequisites</title>
<para>The gitlab service exposes only an Unix socket at
<literal>/run/gitlab/gitlab-workhorse.socket</literal>. You need to configure a
···
</section>
-
<section><title>Configuring</title>
+
<section xml:id="module-services-gitlab-configuring"><title>Configuring</title>
<para>Gitlab depends on both PostgreSQL and Redis and will automatically enable
both services. In the case of PostgreSQL, a database and a role will be created.
···
</section>
-
<section><title>Maintenance</title>
+
<section xml:id="module-services-gitlab-maintenance"><title>Maintenance</title>
<para>You can run Gitlab's rake tasks with <literal>gitlab-rake</literal>
which will be available on the system when gitlab is enabled. You will
+4 -4
nixos/modules/services/misc/taskserver/doc.xml
···
<link xlink:href="https://taskwarrior.org/docs/#taskd"/>
</para>
-
<section>
+
<section xml:id="module-services-taskserver-configuration">
<title>Configuration</title>
<para>
···
</para>
</section>
-
<section>
+
<section xml:id="module-services-taskserver-nixos-taskserver-tool">
<title>The nixos-taskserver tool</title>
<para>
···
<option>--help</option> switch.
</para>
</section>
-
<section>
+
<section xml:id="module-services-taskserver-declarative-ca-management">
<title>Declarative/automatic CA management</title>
<para>
···
<command>task sync</command> after that stage.
</para>
</section>
-
<section>
+
<section xml:id="module-services-taskserver-manual-ca-management">
<title>Manual CA management</title>
<para>
+2 -2
nixos/modules/services/monitoring/prometheus/exporters.xml
···
<para>Prometheus exporters provide metrics for the <link xlink:href="https://prometheus.io">prometheus monitoring system</link>.</para>
-
<section><title>Configuration</title>
+
<section xml:id="module-services-prometheus-exporters-configuration"><title>Configuration</title>
<para>One of the most common exporters is the <link xlink:href="https://github.com/prometheus/node_exporter">node exporter</link>, it provides hardware and OS metrics from the host it's running on. The exporter could be configured as follows:
<programlisting>
services.promtheus.exporters.node = {
···
search through the <link xlink:href="https://nixos.org/nixos/options.html#prometheus.exporters">available options</link>.
</para>
</section>
-
<section><title>Adding a new exporter</title>
+
<section xml:id="module-services-prometheus-exporters-new-exporter"><title>Adding a new exporter</title>
<para>To add a new exporter, it has to be packaged first (see <literal>nixpkgs/pkgs/servers/monitoring/prometheus/</literal> for examples), then a module can be added. The postfix exporter is used in this example:</para>
<itemizedlist>
<listitem>
+4 -4
nixos/modules/services/networking/dnscrypt-proxy.xml
···
upstream is trustworthy).
</para>
-
<sect1><title>Basic configuration</title>
+
<sect1 xml:id="sec-dnscrypt-proxy-configuration"><title>Basic configuration</title>
<para>
To enable the client proxy, set
···
</sect1>
-
<sect1><title>As a forwarder for another DNS client</title>
+
<sect1 xml:id="sec-dnscrypt-proxy-forwarder"><title>As a forwarder for another DNS client</title>
<para>
To run the DNSCrypt proxy client as a forwarder for another
···
</programlisting>
</para>
-
<sect2><title>dnsmasq</title>
+
<sect2 xml:id="sec-dnscrypt-proxy-forwarder-dsnmasq"><title>dnsmasq</title>
<para>
<programlisting>
{
···
</para>
</sect2>
-
<sect2><title>unbound</title>
+
<sect2 xml:id="sec-dnscrypt-proxy-forwarder-unbound"><title>unbound</title>
<para>
<programlisting>
{
+4 -4
nixos/modules/services/web-apps/matomo-doc.xml
···
</para>
-
<section>
+
<section xml:id="module-services-matomo-database-setup">
<title>Database Setup</title>
<para>
···
</section>
-
<section>
+
<section xml:id="module-services-matomo-backups">
<title>Backup</title>
<para>
You only need to take backups of your MySQL database and the
···
</section>
-
<section>
+
<section xml:id="module-services-matomo-issues">
<title>Issues</title>
<itemizedlist>
<listitem>
···
</section>
-
<section>
+
<section xml:id="module-services-matomo-other-web-servers">
<title>Using other Web Servers than nginx</title>
<para>