[taler-docs] branch master updated: setup guide WIP

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 6ed6769  setup guide WIP
6ed6769 is described below

commit 6ed6769fe1b44d643e57a11b7042c017b8b03d00
Author: Florian Dold <florian@dold.me>
AuthorDate: Tue Aug 3 01:47:58 2021 +0200

    setup guide WIP
---
 taler-exchange-setup-guide.rst | 62 ++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 59 insertions(+), 3 deletions(-)

diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index b439310..976eee1 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -200,8 +200,8 @@ The Wire Gateway configuration can be tested with the 
following command:
 
 .. code-block:: shell-session
 
-   [root@exchange-online]# taler-wire-gateway-client --section 
exchange-account-1 --debit-history
-   [root@exchange-online]# taler-wire-gateway-client --section 
exchange-account-1 --credit-history
+   [root@exchange-online]# taler-exchange-wire-gateway-client --section 
exchange-account-1 --debit-history
+   [root@exchange-online]# taler-exchangewire-gateway-client --section 
exchange-account-1 --credit-history
 
 Exchange Database Setup
 =======================
@@ -340,12 +340,68 @@ steps involving the offline signing machine must be 
completed:
 Testing and Troubleshooting
 ===========================
 
+The following shell session illustrates how the wallet can be used to withdraw
+electronic cash from the exchange and subsequently spend it.  For these steps,
+a merchant backend is not required, as the wallet acts as a merchant.
+
+
+.. code-block:: shell-session
+
+  # This will now output a payto URI that money needs to be sent to in order 
to allow withdrawal
+  # of taler coins
+  $ taler-wallet-cli advanced withdraw-manually --exchange $EXCHANGE_URL 
--amount EUR:10.50
+
+  # Show the status of the manual withdrawal operation
+  $ taler-wallet-cli transactions
+
+  #
+  # At this point, a bank transfer to the exchange's bank account
+  # needs to be made with the correct subject / remittance information
+  # as instructed by the wallet after the first step.
+  #
+
+  # Check whether the exchange received an incoming bank transfer
+  [root@exchange-online]# taler-exchangewire-gateway-client --section 
exchange-account-1 --credit-history
+
+  # Once the transfer has been made, try completing the withdrawal
+  $ taler-wallet-cli run-pending
+
+  # Check status of transactions and show balance
+  $ taler-wallet-cli transactions
+  $ taler-wallet-cli balance
+
+  # Now, directly deposit coins with the exchange into a target account
+  # (Usually, a payment is made via a merchant.  The wallet provides
+  # this functionality for testing.)
+  $ taler-wallet-cli deposit create EUR:5 payto://sepa/$IBAN
+
+  # Check if transaction was successful.
+  # (If not, fix issue with exchange and run "run-pending" command again)
+  $ taler-wallet-cli transactions
+
+  # The wallet can also track if the exchange wired the money to the merchant 
account.
+  # The "deposit group id" can be found in the output of the transactions list.
+  $ taler-wallet-cli deposit track $DEPOSIT_GROUP_ID
+
 
 FIXMEs
 ======
 
+* we need to make sure that after every step there is some command
+  that can be executed to make sure the previous step succeeded /
+  the admin is on the right track.
+* We should describe the systemd services that need to be running
 * we should have some summary with the inventory of services that should be 
running
 * how do we know what offline signing steps are still required?  We don't have
   a tool for that ...
-* we need a better way to validate that the exchange is actually working 
correctly
 * when multiple TWGs are configured, which one will be used by the 
taler-exchange-transfer?
+* we should have some tooling to show the current configuration state of the 
exchange,
+  which then tells the admin what to do next (sign keys, configure account, 
configure wire fee),
+  based on the /management and /keys / /wire APIs
+* On Ubuntu focal fossa, I get the following warning on "apt update", are we 
doing something wrong?
+
+  N: Skipping acquire of configured file 'main/binary-i386/Packages' as
+  repository 'https://deb.taler.net/apt/ubuntu focal-fossa InRelease' doesn't
+  support architecture 'i386'
+
+

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.