[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: -fix docs
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: -fix docs |
Date: |
Sat, 09 Sep 2023 16:25:27 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new deec0d85 -fix docs
deec0d85 is described below
commit deec0d8510c86f83a298a85dae87b284fece9c6f
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sat Sep 9 16:25:24 2023 +0200
-fix docs
---
taler-exchange-manual.rst | 6 ++----
taler-merchant-manual.rst | 4 +---
2 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index eea09104..d84214b2 100644
--- 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
index d32c8969..06bb6971 100644
--- 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:
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: -fix docs,
gnunet <=