taler-docs

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

commit f412f08f9bb6943e3e8684cd052350bd4007ba0f
parent 532954590f276c5ebfcf4ee156aef468947b9d72
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Sat, 12 Dec 2020 00:36:23 -0500

mark up ‘db’

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 @@ -327,7 +327,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: