taler-docs

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

commit b8210fad7bee4f452ec837237d5cd6ca29e5b621
parent d0858fc12a3929029add55eebb16c4636e457dfb
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Tue, 22 Dec 2020 10:52:21 -0500

mark up ‘[auditor]’

Diffstat:
Mtaler-auditor-manual.rst | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst @@ -266,7 +266,7 @@ documentation for details. Database -------- -The option ``DB`` under section [auditor] gets the DB backend’s name the +The option ``DB`` under section ``[auditor]`` gets the DB backend’s name the exchange is going to use. So far, only ``DB = postgres`` is supported. After choosing the backend, it is mandatory to supply the connection string (namely, the database name). This is possible in two ways: