remove dangerous taler-config incantations from manual (fixes #7896)

1 files changed, 28 insertions, 17 deletions

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index feaf7783..680dd02c 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -309,9 +309,6 @@ This section discusses configuration options related to the auditor.
 .. include:: frags/configuration-format.rst
 
 
-.. include:: frags/using-taler-config.rst
-
-
 .. _SetupBaseUrl:
 
 Initial configuration
@@ -320,10 +317,11 @@ Initial configuration
 You need to tell the Taler auditor configuration where the
 REST API of the auditor will be available to the public:
 
-.. code-block:: console
+.. code-block:: ini
 
    # Both for the 'offline' *and* the 'auditor' user:
-   $ taler-config -s auditor -o BASE_URL -V https://auditor.example.com/
+   [auditor]
+   BASE_URL = https://auditor.example.com/
 
 The ``helper`` user that is used to download information from the exchange
 needs to know details about the exchange. Similarly, the ``offline`` user
@@ -332,11 +330,12 @@ need to obtain the ``MASTER_PUBLIC_KEY`` from the exchange operator (they need
 to run ``taler-exchange-offline setup``) and the REST endpoint of the exchange
 and configure these:
 
-.. code-block:: console
+.. code-block:: ini
 
    # As the 'helper' and 'offline' users:
-   $ taler-config -s exchange -o BASE_URL -V https://exchange.example.com/
-   $ taler-config -s exchange -o MASTER_PUBLIC_KEY -V $SOMELONGBASE32VALUEHERE
+   [exchange]
+   BASE_URL = https://exchange.example.com/
+   MASTER_PUBLIC_KEY = $SOMELONGBASE32VALUEHERE
 
 
 .. _AuditorKeys:
@@ -372,10 +371,11 @@ of the ``auditor`` user in the ``[auditor]]`` configuration section:
 
 You can set this configuration value using:
 
-.. code-block:: console
+.. code-block:: ini
 
    # As the 'auditor' and 'helper' users:
-   $ taler-config -s auditor -o PUBLIC_KEY -V $SOMELONGBASE32VALUEHERE
+   [auditor]
+   PUBLIC_KEY = $SOMELONGBASE32VALUEHERE
 
 
 .. _AuditorServing:
@@ -658,11 +658,16 @@ PostgreSQL configuration:
 Next, the ``postgres`` user of the auditor's system must first initialize the
 local tables:
 
-.. code-block:: console
+.. code-block:: ini
 
+   # Configure database:
+   [exchange]
+   DB = "postgres"
+   [exchangedb-postgres]
+   CONFIG = "postgres:///taler-ingress"
+
+.. code-block:: console
    # As the 'ingress' user of the exchange:
-   $ taler-config -s exchange -o DB -V "postgres"
-   $ taler-config -s exchangedb-postgres -o CONFIG -V "postgres:///taler-ingress"
    $ taler-exchange-dbinit
 
 To complete the replication, the ``postgres`` user of the auditor's
@@ -722,11 +727,17 @@ needs to be changed.
 To run ``taler-auditor-sync``, you must first configure two configuration
 files that identify the source and destination databases:
 
-.. code-block:: console
+.. code-block:: ini
 
-   # As the 'sync' user:
-   $ taler-config -c src.conf -s exchangedb -o CONFIG -V "postgres:///auditor-ingres/"
-   $ taler-config -c dst.conf -s exchangedb -o CONFIG -V "postgres:///auditor/"
+   # src.conf
+   [exchangedb]
+   CONFIG = "postgres:///auditor-ingres/"
+
+.. code-block:: ini
+
+   # dst.conf
+   [exchangedb]
+   CONFIG = "postgres:///auditor/"
 
 Now you should be able to launch the synchronization process. You can run
 the process via systemd in the background. For a first one-off test, you should