sinavir
/
liminix
forked from dan/liminix
1
0
Fork 0
Code Pull Requests Activity

improve syntax blah

This commit is contained in:
Daniel Barlow 2023-09-17 16:33:29 +01:00
parent 06b725cb77
commit fc84435985
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/configuration.rst
View File

@ -1,10 +1,10 @@
Configuration and Module Guide Configuration and Module Guide
############################## ##############################
Liminix uses the Nix language to provide congruent configuration. Liminix uses the Nix language to provide congruent configuration
This means that to change anything about the way in which a management. This means that to change anything about the way in
Liminix system works, you make that change in which a Liminix system works, you make that change in
:file:`configuration.nix` (or one of the other files it references) your :file:`configuration.nix` (or one of the other files it references),
and rerun :command:`nix-build` or :command:`liminix-rebuild` to action and rerun :command:`nix-build` or :command:`liminix-rebuild` to action
the change. It is not possible (at least, without shenanigans) to make the change. It is not possible (at least, without shenanigans) to make
changes by logging into the device and running imperative commands changes by logging into the device and running imperative commands
@ -89,9 +89,9 @@ domains, or you want to run two SSH daemons on different ports.
Services Services
******** ********
We use the s6/s6-rc system to start/stop/restart services and handle We use the `s6-rc service manager <https://www.skarnet.org/software/s6-rc/overview.html>`_ to start/stop/restart services and handle
service dependencies. Any attribute in `config.services` will become service dependencies. Any attribute in `config.services` will become
part of the default set of services that s6 will try to bring up on part of the default set of services that s6-rc will try to bring up on
boot. boot.
For the most part, for common use cases, hopefully the services you For the most part, for common use cases, hopefully the services you
@ -104,8 +104,8 @@ the `oneshot` or `longrun` functions:
* a "longrun" service is the "normal" service concept: it has a * a "longrun" service is the "normal" service concept: it has a
``run`` action which describes the process to start, and it watches ``run`` action which describes the process to start, and it watches
that process to restart it if it exits. The process should not that process to restart it if it exits. The process should not
attempt to daemonize or "background" itself, otherwise s6 will think attempt to daemonize or "background" itself, otherwise s6-rc will think
it died. . Whatever it prints to standard output/standard error it died. Whatever it prints to standard output/standard error
will be logged. will be logged.
.. code-block:: nix .. code-block:: nix