[taler-docs] 35/36: update manuals

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

commit f47314fe9460324d5bf331d0dc71d5358c6d8e08
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Tue Jun 22 19:34:20 2021 +0200

    update manuals
---
 taler-auditor-manual.rst  | 17 +++++++++++++++--
 taler-exchange-manual.rst |  2 +-
 2 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 6cd3022..c6d73c0 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -227,7 +227,7 @@ To install the Taler exchange, you can now simply run:
 
 .. code-block:: console
 
-   # apt install -t focal-fossa taler-exchange
+   # apt install -t focal-fossa taler-auditor
 
 For the auditor, you must manually configure access to the exchange database,
 the HTTP reverse proxy (typically with TLS certificates) and offline signing.
@@ -250,6 +250,19 @@ This section discusses configuration options related to 
the auditor.
 .. include:: frags/using-taler-config.rst
 
 
+.. _SetupBaseUrl:
+
+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
+
+   # taler-config -s auditor -o BASE_URL -V https://auditor.example.com/
+
+
 .. _AuditorKeys:
 
 Keys
@@ -312,7 +325,7 @@ choosing the backend, it is mandatory to supply the 
connection string
 
 -  via an environment variable: ``TALER_AUDITORDB_POSTGRES_CONFIG``.
 
--  via configuration option ``CONFIG``, under section ``[auditordb-BACKEND]``.
+-  via configuration option ``CONFIG``, under section ``[auditordb-$BACKEND]``.
    For example, the demo exchange is configured as follows:
 
    .. code-block:: ini
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 4e2863d..c28ddaa 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -442,7 +442,7 @@ choosing the backend, it is mandatory to supply the 
connection string
 
 -  via an environment variable: ``TALER_EXCHANGEDB_POSTGRES_CONFIG``.
 
--  via configuration option ``CONFIG``, under section ``[exchangedb-BACKEND]``.
+-  via configuration option ``CONFIG``, under section 
``[exchangedb-$BACKEND]``.
    For example, the demo exchange is configured as follows:
 
 .. code-block:: ini

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.