From ea4bfb4f8903c2cb73f82b4f940323af745bf2b9 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Fri, 4 Dec 2020 04:06:16 -0500 Subject: use ‘.. code-block:: console’ (88 instances) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-auditor-manual.rst | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) (limited to 'taler-auditor-manual.rst') diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 35f5a799..8faadb6a 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -221,7 +221,7 @@ to export some of the tooling required by Taler. To download and install libgnunetutil, proceed as follows: -:: +.. code-block:: console $ git clone https://git.gnunet.org/gnunet/ $ cd gnunet/ @@ -237,7 +237,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 @@ -370,9 +370,9 @@ If this step is skipped, the auditor will malfunction at all future stages with a foreign key violation, as it doesn't know the exchange's master public key. -:: +.. code-block:: console - taler-auditor-exchange -m $MASTER_PUB -u $EXCHANGE_BASE_URL + $ taler-auditor-exchange -m $MASTER_PUB -u $EXCHANGE_BASE_URL .. _AuditorDenominations: @@ -392,9 +392,9 @@ receive the blob to sign (Website, manual delivery, ...). Note that the blob does not contain confidential data, but signing the wrong keys would be fatal. Given the blob, the auditor would sign it using: -:: +.. 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. @@ -467,7 +467,7 @@ Performing an audit is done by invoking the ``taler-auditor`` and files, which can then be combined using the ``contrib/render.py`` script into the TeX report. -:: +.. code-block:: console $ taler-audit @@ -510,7 +510,7 @@ several categories of failures of different severity: the correct amount to a merchant). - Configuration issues (such was wire fees unavailable) - + .. _AuditorDatabaseUpgrades: @@ -520,9 +520,9 @@ Database upgrades To upgrade the database between Taler versions can be done by running: -:: +.. code-block:: console - $ taler-auditor-dbinit + $ taler-auditor-dbinit However, the above is the general rule. Please review the specific release notes to ensure this is correct for the @@ -531,7 +531,7 @@ specific upgrade. The auditor database can be re-initialized using: -:: +.. code-block:: console $ taler-auditor-dbinit -r @@ -654,7 +654,7 @@ CodeBlau reports the following checks: coin value without fee, total deposit without refunds - wire out fee is negative - + - coin arithmetic inconsistencies - refund (merchant) is negative @@ -672,13 +672,13 @@ CodeBlau reports the following checks: - wire out inconsistencies in amount - row inconsistencies - + - wire account given is malformed - h(wire) does not match wire - failed to compute hash of given wire data - + - database contains wrong hash code for wire details - no transaction history for coin claimed in aggregation @@ -715,7 +715,7 @@ CodeBlau reports the following checks: - arithmetic inconsistencies - melt contribution vs. fee - + - melt (cost) - refund fee -- cgit v1.2.3 From 5a334dedaa1dce9f82cc010e342292229ad5d236 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Fri, 4 Dec 2020 04:25:20 -0500 Subject: use ‘.. code-block:: ini’ (14 instances) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-auditor-manual.rst | 2 +- taler-backoffice-manual.rst | 2 +- taler-exchange-manual.rst | 10 +++++----- taler-merchant-manual.rst | 16 ++++++++-------- 4 files changed, 15 insertions(+), 15 deletions(-) (limited to 'taler-auditor-manual.rst') diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 8faadb6a..432e2d1e 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -320,7 +320,7 @@ choosing the backend, it is mandatory to supply the connection string - via configuration option CONFIG, under section [auditordb-BACKEND]. For example, the demo exchange is configured as follows: -:: +.. code-block:: ini [auditor] ... diff --git a/taler-backoffice-manual.rst b/taler-backoffice-manual.rst index d9c57f2c..3042845d 100644 --- a/taler-backoffice-manual.rst +++ b/taler-backoffice-manual.rst @@ -63,7 +63,7 @@ read: https://docs.taler.net/exchange/html/taler-exchange.html#Configuration-format), a working configuration example is the following one: -:: +.. code-block:: ini [taler] # will be EUR, USD, or whatever currency the merchant diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst index 7e132d79..4d19709e 100644 --- a/taler-exchange-manual.rst +++ b/taler-exchange-manual.rst @@ -311,7 +311,7 @@ it under $HOME/.config/. A config file is a text file containing sections, and each section contains its values. The right format follows: -:: +.. code-block:: ini [section1] value1 = string @@ -330,7 +330,7 @@ variables that are unset, by using the following syntax: by defining them under a ``[paths]`` section, see example below, -:: +.. code-block:: ini [paths] TALER_DEPLOYMENT_SHARED = ${HOME}/shared-data @@ -496,7 +496,7 @@ starting with “exchange-account-” for the section name. You can ENABLE for each account whether it should be used, and for what (incoming or outgoing wire transfers): -:: +.. code-block:: ini [exchange-account-1] # With x-taler-bank (say for PyBank) @@ -554,7 +554,7 @@ apply whenever the exchange closes a reserve (sending back funds to the customer). The fees must be constant for a full year, which is specified as part of the name of the option. -:: +.. code-block:: ini [fees-iban] WIRE-FEE-2018 = EUR:0.01 @@ -583,7 +583,7 @@ choosing the backend, it is mandatory to supply the connection string - via configuration option CONFIG, under section [exchangedb-BACKEND]. For example, the demo exchange is configured as follows: -:: +.. code-block:: ini [exchange] ... diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst index bf69c499..aecc56a5 100644 --- a/taler-merchant-manual.rst +++ b/taler-merchant-manual.rst @@ -527,7 +527,7 @@ Service address The following option sets the transport layer address used by the merchant backend: - :: +.. code-block:: ini [MERCHANT]/SERVE = TCP | UNIX @@ -560,7 +560,7 @@ Currency Which currency the Web shop deals in, i.e. “EUR” or “USD”, is specified using the option - :: +.. code-block:: ini [TALER]/CURRENCY @@ -579,7 +579,7 @@ Database In principle is possible for the backend to support different DBMSs. The option - :: +.. code-block:: ini [MERCHANT]/DB @@ -591,7 +591,7 @@ DBMS-specific options to access the database. For postgres, you need to provide: - :: +.. code-block:: ini [MERCHANTDB-postgres]/CONFIG @@ -734,7 +734,7 @@ Sample backend configuration The following is an example for a complete backend configuration: - :: +.. code-block:: ini [TALER] CURRENCY = KUDOS @@ -1347,7 +1347,7 @@ it under ``$HOME/.config/``. A config file is a text file containing sections, and each section contains its values. The right format follows: -:: +.. code-block:: ini [section1] value1 = string @@ -1366,11 +1366,11 @@ variables that are unset, by using the following syntax: by defining them under a ``[paths]`` section, see example below, -:: +.. code-block:: ini [paths] TALER_DEPLOYMENT_SHARED = ${HOME}/shared-data - .. + ... [section-x] path-x = ${TALER_DEPLOYMENT_SHARED}/x -- cgit v1.2.3