taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit c7d618d831cf8892551fefc19770077ef59781a5
parent 42d193aeb7914673d49ba4bf18ffd1db5274803a
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Thu, 22 Dec 2016 16:26:42 +0100

Merge branch 'master' of ssh://taler.net/api

Diffstat:
Mdeployment.rst | 16++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/deployment.rst b/deployment.rst @@ -199,13 +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. -The exchange needs to get its database explicitly set up, before it can -actually be launched. +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: