[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: db instruction order
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: db instruction order |
Date: |
Fri, 06 Aug 2021 15:25:18 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 5293c62 db instruction order
5293c62 is described below
commit 5293c62b066d8106816d2f270876e21056363782
Author: Florian Dold <florian@dold.me>
AuthorDate: Fri Aug 6 15:25:13 2021 +0200
db instruction order
---
taler-exchange-setup-guide.rst | 45 ++++++++++++++++++++++++++----------------
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index a3babed..af93978 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -741,7 +741,28 @@ This will create a ``taler-exchange`` database owned by the
``taler-exchange-httpd`` user. We will use that user later to perform
database maintenance operations.
-Next, we need to grant the other accounts limited access:
+
+Assuming the above database setup, the database credentials to configure
+in the configuration file would simply be:
+
+.. code-block:: ini
+ :caption: /etc/taler/secrets/exchange-db.secret.conf
+
+ [exchangedb-postgres]
+ CONFIG=postgres:///taler-exchange
+
+
+If the database is run on a different host, please follow the instructions
+from the Postgres manual for configuring remote access.
+
+After configuring the database credentials, the exchange database needs
+to be initialized with the following command:
+
+.. code-block:: shell-session
+
+ [root@exchange-online]# sudo -u taler-exchange-httpd taler-exchange-dbinit
+
+Finally we need to grant the other accounts limited access:
.. code-block:: shell-session
@@ -763,26 +784,16 @@ Next, we need to grant the other accounts limited access:
message after the execution. This might be avoided by first getting a shell
as the taler-exchange-httpd user
and then run the SQL statements.
+.. note::
-Assuming the above database setup, the database credentials to configure
-in the configuration file would simply be:
-
-.. code-block:: ini
- :caption: /etc/taler/secrets/exchange-db.secret.conf
-
- [exchangedb-postgres]
- CONFIG=postgres:///taler-exchange
-
+ The above instructions for changing database permissions only work *after*
+ having initialized the database with ``taler-exchange-dbinit``, as
+ the tables to exist before permissions can be granted on them.
-If the database is run on a different host, please follow the instructions
-from the Postgres manual for configuring remote access.
-
-After configuring the database credentials, the exchange database needs
-to be initialized with the following command:
+..
-.. code-block:: shell-session
+ FIXME: Why don't we grant the permissions to the schema / database then?
- [root@exchange-online]# sudo -u taler-exchange-httpd taler-exchange-dbinit
Offline Signing Setup
--
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: db instruction order,
gnunet <=