taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 2d44c7138315e815ed6f1a944aa29202839dfd8d
parent 5c6f937a6d199eb5a78b19dc91f504b62cb31caf
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Tue, 22 Dec 2020 11:05:09 -0500

indent code block

Diffstat:
Mtaler-auditor-manual.rst | 14+++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst @@ -276,15 +276,15 @@ choosing the backend, it is mandatory to supply the connection string - via configuration option ``CONFIG``, under section ``[auditordb-BACKEND]``. For example, the demo exchange is configured as follows: -.. code-block:: ini + .. code-block:: ini - [auditor] - ... - DB = postgres - ... + [auditor] + ... + DB = postgres + ... - [auditordb-postgres] - CONFIG = postgres:///auditordemo + [auditordb-postgres] + CONFIG = postgres:///auditordemo If an exchange runs its own auditor, it may use the same database for the auditor and the exchange itself.