commit deec0d8510c86f83a298a85dae87b284fece9c6f
parent e768b1ac5122e1619e9fd762e0168de4c22208ce
Author: Christian Grothoff <christian@grothoff.org>
Date: Sat, 9 Sep 2023 16:25:24 +0200
-fix docs
Diffstat:
2 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
@@ -549,10 +549,8 @@ this group.
The **taler-exchange-dbconfig** tool can be used to automate the database
setup. When using the Debian/Ubuntu packages, the users 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-exchange-dbinit** (as the ``taler-exchange-httpd`` user) to
- initialize the database schema and then grant access to
- the other users (see below).
+ have a working database configuration. Subsequently, must still grant
+ access to the other users (see below). (NOTE: we should automate this.)
To create a database for the Taler exchange on the local system, run:
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -518,9 +518,7 @@ DBMS-specific options to access the database.
The **taler-merchant-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-merchant-dbinit** as the ``taler-merchant-httpd`` user to
- initialize the database schema.
+ have a working database configuration.
For the ``postgres`` backend, you need to specify:
