nixos/*: convert multiline inline code to listings
presumably it was not intended to have these blocks rendered inline, and markdown conversion would be messy as well.
This commit is contained in:
parent
0cfcb5908c
commit
7d102d113a
8 changed files with 24 additions and 24 deletions
|
@ -68,12 +68,12 @@ in
|
|||
like datacenter. The tiers and order must be the same on all nodes.
|
||||
Including more tiers is better than including fewer. For example:
|
||||
|
||||
<literal>
|
||||
<programlisting>
|
||||
country=us,region=us-west,datacenter=us-west-1b,rack=12
|
||||
country=ca,region=ca-east,datacenter=ca-east-2,rack=4
|
||||
|
||||
planet=earth,province=manitoba,colo=secondary,power=3
|
||||
</literal>
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
|
@ -72,9 +72,9 @@ in with lib; {
|
|||
values, you can run the <command>lsusb</command> command. Example
|
||||
output:
|
||||
|
||||
<literal>
|
||||
<programlisting>
|
||||
Bus 005 Device 002: ID 0403:c630 Future Technology Devices International, Ltd lcd2usb interface
|
||||
</literal>
|
||||
</programlisting>
|
||||
|
||||
In this case the vendor id is 0403 and the product id is c630.
|
||||
'';
|
||||
|
|
|
@ -29,9 +29,9 @@ let
|
|||
The log file to be scanned.
|
||||
|
||||
For mail, set this to
|
||||
<literal>
|
||||
<programlisting>
|
||||
journalctl $OLD_CURSOR -u postfix.service | ''${pkgs.perl}/bin/perl ''${pkgs.awstats.out}/share/awstats/tools/maillogconvert.pl standard |
|
||||
</literal>
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
|
||||
|
@ -42,9 +42,9 @@ let
|
|||
The log format being used.
|
||||
|
||||
For mail, set this to
|
||||
<literal>
|
||||
<programlisting>
|
||||
%time2 %email %email_r %host %host_r %method %url %code %bytesd
|
||||
</literal>
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
|
@ -23,17 +23,17 @@ in {
|
|||
|
||||
Example users file with plain-text passwords:
|
||||
|
||||
<literal>
|
||||
<programlisting>
|
||||
test1:CL:password1
|
||||
test2:CL:password2
|
||||
</literal>
|
||||
</programlisting>
|
||||
|
||||
Example users file with md5-crypted passwords:
|
||||
|
||||
<literal>
|
||||
<programlisting>
|
||||
test1:CR:$1$tFkisVd2$1GA8JXkRmTXdLDytM/i3a1
|
||||
test2:CR:$1$rkpibm5J$Aq1.9VtYAn0JrqZ8M.1ME.
|
||||
</literal>
|
||||
</programlisting>
|
||||
|
||||
You can generate md5-crypted passwords via https://unix4lyfe.org/crypt/
|
||||
Note that htpasswd tool generates incompatible md5-crypted passwords.
|
||||
|
@ -130,7 +130,7 @@ in {
|
|||
|
||||
Double authentication is possible, e.g.
|
||||
|
||||
<literal>
|
||||
<programlisting>
|
||||
{
|
||||
auth = [ "iponly" "strong" ];
|
||||
acl = [
|
||||
|
@ -144,7 +144,7 @@ in {
|
|||
}
|
||||
];
|
||||
}
|
||||
</literal>
|
||||
</programlisting>
|
||||
In this example strong username authentication is not required to access 192.168.0.0/16.
|
||||
'';
|
||||
};
|
||||
|
|
|
@ -180,13 +180,13 @@ in
|
|||
readable only by the <literal>uucp</literal> user.
|
||||
See hosts.hfaxd(5) for details.
|
||||
This configuration permits access for all users:
|
||||
<literal>
|
||||
<programlisting>
|
||||
environment.etc."hosts.hfaxd" = {
|
||||
mode = "0600";
|
||||
user = "uucp";
|
||||
text = ".*";
|
||||
};
|
||||
</literal>
|
||||
</programlisting>
|
||||
Note that host-based access can be controlled with
|
||||
<option>config.systemd.sockets.hylafax-hfaxd.listenStreams</option>;
|
||||
by default, only 127.0.0.1 is permitted to connect.
|
||||
|
|
|
@ -49,7 +49,7 @@ in {
|
|||
the database yourself.
|
||||
|
||||
Example:
|
||||
<literal>
|
||||
<programlisting>
|
||||
services.postgresql = {
|
||||
enable = true;
|
||||
ensureDatabases = [ "hockeypuck" ];
|
||||
|
@ -58,7 +58,7 @@ in {
|
|||
ensurePermissions."DATABASE hockeypuck" = "ALL PRIVILEGES";
|
||||
}];
|
||||
};
|
||||
</literal>
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
};
|
||||
|
|
|
@ -19,9 +19,9 @@ in {
|
|||
This enables LXCFS, a FUSE filesystem for LXC.
|
||||
To use lxcfs in include the following configuration in your
|
||||
container configuration:
|
||||
<code>
|
||||
virtualisation.lxc.defaultConfig = "lxc.include = ''${pkgs.lxcfs}/share/lxc/config/common.conf.d/00-lxcfs.conf";
|
||||
</code>
|
||||
<programlisting>
|
||||
virtualisation.lxc.defaultConfig = "lxc.include = ''${pkgs.lxcfs}/share/lxc/config/common.conf.d/00-lxcfs.conf";
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
};
|
||||
|
|
|
@ -26,9 +26,9 @@ in {
|
|||
|
||||
Most of the time, you'll also want to start lxcfs, so
|
||||
that containers can "see" the limits:
|
||||
<code>
|
||||
virtualisation.lxc.lxcfs.enable = true;
|
||||
</code>
|
||||
<programlisting>
|
||||
virtualisation.lxc.lxcfs.enable = true;
|
||||
</programlisting>
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
Loading…
Reference in a new issue