taler-docs

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

mark up ‘TALER_AUDITORDB_POSTGRES_CONFIG’

Diffstat:
M
taler-auditor-manual.rst
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
@@ -332,7 +332,7 @@ 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:
 
--  via an environment variable: TALER_AUDITORDB_POSTGRES_CONFIG.
+-  via an environment variable: ``TALER_AUDITORDB_POSTGRES_CONFIG``.
 
 -  via configuration option CONFIG, under section [auditordb-BACKEND].
    For example, the demo exchange is configured as follows: