aboutsummaryrefslogtreecommitdiff
path: root/taler-challenger-manual.rst
diff options
context:
space:
mode:
authorChristian Grothoff <grothoff@gnunet.org>2023-09-07 16:58:15 +0200
committerChristian Grothoff <grothoff@gnunet.org>2023-09-07 16:58:15 +0200
commite768b1ac5122e1619e9fd762e0168de4c22208ce (patch)
tree740526858789b3449e15ded9200fc03708e55f9d /taler-challenger-manual.rst
parentec5b3b16426edcd0734db9e11104191048ad59ce (diff)
downloaddocs-e768b1ac5122e1619e9fd762e0168de4c22208ce.tar.gz
docs-e768b1ac5122e1619e9fd762e0168de4c22208ce.tar.bz2
docs-e768b1ac5122e1619e9fd762e0168de4c22208ce.zip
update installation manuals|
Diffstat (limited to 'taler-challenger-manual.rst')
-rw-r--r--taler-challenger-manual.rst14
1 files changed, 12 insertions, 2 deletions
diff --git a/taler-challenger-manual.rst b/taler-challenger-manual.rst
index 78c723cf..ae7eb047 100644
--- a/taler-challenger-manual.rst
+++ b/taler-challenger-manual.rst
@@ -247,6 +247,16 @@ The access credentials for the Challenger database are configured in
``/etc/challenger/challenger.conf``. Currently, only PostgreSQL is
supported as a database backend.
+.. note::
+
+ The **challenger-dbconfig** tool can be used to automate the database
+ setup. When using the Debian/Ubuntu packages, the user should already have
+ been created, so you can just run the tool without any arguments and should
+ have a working database configuration. Subsequently, you should still run
+ **taler-challenger-dbinit** as the ``challenger-httpd`` user to
+ initialize the database schema.
+
+
To create a database for Challenger on the local system, run:
.. code-block:: shell-session
@@ -279,7 +289,7 @@ to be initialized with the following command:
.. code-block:: shell-session
- [root@exchange-online]# sudo -u challenger-httpd challenger
+ [root@exchange-online]# sudo -u challenger-httpd challenger-dbinit
..note::
@@ -475,7 +485,7 @@ The Challenger database can be re-initialized using:
.. code-block:: console
- $ taler-exchange-dbinit --reset
+ $ challenger-dbinit --reset
However, running this command will result in all data in the database
being lost.