[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 02/03: mark up ‘TALER_AUDITORDB_POSTGRES_CONFIG’
From: |
gnunet |
Subject: |
[taler-docs] 02/03: mark up ‘TALER_AUDITORDB_POSTGRES_CONFIG’ |
Date: |
Sat, 12 Dec 2020 06:39:10 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
commit 42ec6a89bbf4c2f29d8f1559ae9975b0919d2006
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Dec 12 00:36:44 2020 -0500
mark up ‘TALER_AUDITORDB_POSTGRES_CONFIG’
---
taler-auditor-manual.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index e396394..87c6ea9 100644
--- 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:
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.