doc: deployment: manual and fixes

diff --git a/doc/deployment-advanced.rst b/doc/deployment-advanced.rst
index 0dc27d49ef0e74d4c18d933d8dbfe73578bd7565..8b39b23fa912022a28db32cb1f7a8ffa2ff8de93 100644 (file)
--- a/doc/deployment-advanced.rst
+++ b/doc/deployment-advanced.rst
@@ -6,4 +6,4 @@ Advanced
    :maxdepth: 2
    
    deployment-advanced-no-manager
-   config-no-systemd
\ No newline at end of file
+   deployment-no-systemd
\ No newline at end of file

diff --git a/doc/deployment-manual.rst b/doc/deployment-manual.rst
index 48fa0d1125ba61ec4a0673151cc27cf75d7601a6..5d05847d8db0b9e2d8692fdedff6092d0cd12833 100644 (file)
--- a/doc/deployment-manual.rst
+++ b/doc/deployment-manual.rst
@@ -2,4 +2,6 @@
 Manual
 ******
 
-TODO how to run it manually without systemd, what are the requirements
\ No newline at end of file
+The Knot Resolver can be started with the command ``knot-resolver``. You can provide an optional argument ``--config path/to/config.yml`` to load a different than default configuration file.
+
+The resolver does not have any external runtime dependencies and it should be able to run in most environments. The resolver does not interact with cgroups or namespaces and you can run it multiple times as long as you use a different runtime directory in the configuration.
\ No newline at end of file

diff --git a/doc/deployment-no-systemd.rst b/doc/deployment-no-systemd.rst
index 6aeb142e154192a98b4a65ffd6da1421bfae4f1c..ff5f94513cee805f5be2a52ed4c7893c7996c527 100644 (file)
--- a/doc/deployment-no-systemd.rst
+++ b/doc/deployment-no-systemd.rst
@@ -3,7 +3,7 @@
 .. _usage-without-systemd:
 
 *****************************************
-Usage without systemd and without systemd
+Usage without systemd and without manager
 *****************************************
 
 .. tip:: Our upstream packages use systemd integration, which is the recommended