diff options
Diffstat (limited to 'taler-exchange-manual.rst')
| -rw-r--r-- | taler-exchange-manual.rst | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst index 0b038216..7e132d79 100644 --- a/taler-exchange-manual.rst +++ b/taler-exchange-manual.rst @@ -257,7 +257,7 @@ to export some of the tooling required by Taler. To download and install libgnunetutil, proceed as follows: -:: +.. code-block:: console $ git clone git://git.gnunet.org/gnunet $ cd gnunet/ @@ -273,7 +273,7 @@ which requires you to run the last step as ``root``. To download and install the GNU Taler exchange, proceeds as follows: -:: +.. code-block:: console $ git clone git://git.taler.net/exchange $ cd exchange @@ -340,7 +340,7 @@ by defining them under a ``[paths]`` section, see example below, or by setting them in the environment: -:: +.. code-block:: console $ export VAR=/x @@ -378,7 +378,7 @@ file format and can also be edited by hand. Run -:: +.. code-block:: console $ taler-config -s $SECTION @@ -386,7 +386,7 @@ to list all of the configuration values in section ``$SECTION``. Run -:: +.. code-block:: console $ taler-config -s $section -o $option @@ -395,7 +395,7 @@ section ``$section``. Finally, to change a setting, run -:: +.. code-block:: console $ taler-config -s $section -o $option -V $value @@ -408,7 +408,7 @@ their value. To expand the ``$DATADIR`` or other $-variables in the configuration, pass the ``-f`` option to ``taler-config``. For example, compare: -:: +.. code-block:: console $ taler-config -s ACCOUNT-bank \ -o WIRE_RESPONSE @@ -530,7 +530,7 @@ The command line tool taler-exchange-wire is used to create the follows to create all of the WIRE_RESPONSE files (in the locations specified by the configuration): -:: +.. code-block:: console $ taler-exchange-wire @@ -741,9 +741,9 @@ by the tool ``taler-exchange-keyup``. The following command generates denomkeys and signkeys, plus the "blob" that is to be signed by the auditor. -:: +.. code-block:: console - taler-exchange-keyup -o blob + $ taler-exchange-keyup -o blob *blob* contains data about denomkeys that the exchange operator needs to get signed by every auditor he wishes (or is forced to) work with. @@ -753,9 +753,9 @@ blob to sign (Website, manual delivery, ..). Nonetheless, the exchange admin can fake an auditor signature — for testing purposes — by running the following command -:: +.. code-block:: console - taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE + $ taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE Those arguments are all mandatory. @@ -775,9 +775,9 @@ option ``AUDITOR_BASE_DIR`` under the section ``[exchangedb]``. Assuming following command will "add" the auditor identified by ``AUDITOR_URL`` to the exchange. -:: +.. code-block:: console - cp OUTPUT_FILE ${HOME}/.local/share/taler/auditors + $ cp OUTPUT_FILE ${HOME}/.local/share/taler/auditors If the auditor has been correctly added, the exchange’s ``/keys`` response must contain an entry in the ``auditors`` array mentioning the @@ -793,7 +793,7 @@ versions. The exchange database can be re-initialized using: -:: +.. code-block:: console $ taler-exchange-dbinit -r @@ -1008,7 +1008,7 @@ initialized using ``taler-exchange-keyup``. You can run a first simple benchmark using: -:: +.. code-block:: console $ createdb talercheck # if it does not yet exist $ taler-exchange-keyup -c benchmark.conf |