taler-docs

commit 89a116626146493c36d11822ede6e01959e7645c
parent 14e82828e42307265dacba51073931f798924441
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Wed, 21 Dec 2016 22:43:20 +0100

dbinit instructions

Diffstat:
M
deployment.rst
 | 
19
+++++++++++++++++++

1 file changed, 19 insertions(+), 0 deletions(-)
diff --git a/deployment.rst b/deployment.rst
@@ -199,6 +199,25 @@ The next step is to generate `signkeys` and `denomkeys`.
   policy of 12-chars limit for currency names; which is likely going to
   be changed.
 
+It may be necessary to define database tables for the exchange.  The
+following command does that.
+
+.. code-block:: none
+
+  # Erase all the data!
+  $ taler-exchange-dbinit -r
+
+As of the merchant backend, it creates tables at launch time, so it is
+not required to define tables before launching it.  `However`, if some
+table's definition changed over the time, and there is a need to force
+a redefinition of tables, then the following command accomplishes that
+for the merchant:
+
+.. code-block:: none
+
+  # Erase all the data!
+  $ taler-merchant-dbinit -r
+
 If all previous steps succeeded, it is now possible to launch all the
 processes.  That is accomplished by the following command: