begin to document benchmark setup

1 files changed, 34 insertions, 3 deletions

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index a064efce..d6ea1bf7 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -1221,6 +1221,40 @@ Benchmarking
 
 NOTE: This section is dated and should be reviewed!
 
+Setup: create Exchange account and two user accounts ``42`` and ``43`` at
+the bank:
+
+::
+
+   $ taler-bank-manage django add_bank_account Exchange
+   $ taler-bank-manage django add_bank_account 42
+   $ taler-bank-manage django add_bank_account 43
+
+Setup exchange password using:
+
+::
+
+   $ taler-bank-manage django changepassword_unsafe Exchange PASSWORD
+
+Configure merchant and exchange, then run:
+
+::
+
+   $ taler-exchange-dbinit
+   $ taler-exchange-keyup
+   $ taler-merchant-dbinit
+
+Launch bank, exchange and merchant backends:
+
+::
+
+   $ taler-bank-manage serve-http
+   $ taler-exchange-httpd
+   $ taler-merchant-httpd
+
+
+
+
 The merchant codebase offers the ``taler-merchant-benchmark`` tool to
 populate the database with fake payments. This tool is in charge of
 starting a merchant, exchange, and bank processes, and provide them all
@@ -1230,9 +1264,6 @@ own configuration (as they would do in production).
 The tool takes all of the values it needs from the command line, with
 some of them being mandatory. Among those, we have:
 
--  ``--currency=K`` Use currency *K*, for example to craft coins to
-   withdraw.
-
 -  ``--bank-url=URL`` Assume that the bank is serving under the base URL
    *URL*. This option is only actually used by the tool to check if the
    bank was well launched.