taler-docs

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

commit fc5c254a18869fd112aaf8ae950caf24c4bbc4d4
parent e0e875d6fbf5ce38a12b06104f10f145e739cc60
Author: Florian Dold <florian@dold.me>
Date:   Thu,  5 Aug 2021 00:11:56 +0200

update setup guide FIXMEs

Diffstat:
Mtaler-exchange-setup-guide.rst | 15++++-----------
1 file changed, 4 insertions(+), 11 deletions(-)

diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst @@ -567,17 +567,10 @@ TBD. 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 ... -* 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 +* We should have some summary with the inventory of services that should be + running. Systemd by default doesn't show this nicely. Maybe suggest running + "systemd list-dependencies taler-exchange.target"? +* When multiple TWGs are configured, which one will be used by the taler-exchange-transfer? * 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