taler-docs

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

commit da863232486aee72eebf3f76000329f27e5163f5
parent 149de84d66c86fdd324bb4fe6eb239651c69b78a
Author: Florian Dold <florian.dold@gmail.com>
Date:   Tue, 24 Mar 2020 18:07:54 +0530

clarifications

Diffstat:
Mtaler-wallet.rst | 7++++++-
1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/taler-wallet.rst b/taler-wallet.rst @@ -87,6 +87,10 @@ Integration Test Example Integration tests can be done with the low-level wallet commands. To select which coins and denominations to use, the wallet can dump the coins in an easy-to-process format (`CoinDumpJson <https://git.taler.net/wallet-core.git/tree/src/types/talerTypes.ts#n734>`__). +The database file for the wallet can be selected with the ``--wallet-db`` +option. This option must be passed to the ``taler-wallet-cli`` command and not +the subcommands. If the database file doesn't exist, it will be created. + The following example does a simple withdrawal recoup: .. code-block:: sh @@ -132,7 +136,8 @@ To test refreshing, force a refresh: $ taler-wallet-cli --wallet-db=mydb.json advanced force-refresh "$coin_pub" -To test zombie coins, use the timetravel option, it **must** be passed to the top-level command and not the subcommand: +To test zombie coins, use the timetravel option. It **must** be passed to the +top-level command and not the subcommand: .. code-block:: sh