summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-08-01 12:24:25 +0200
committerChristian Grothoff <christian@grothoff.org>2021-08-01 12:24:25 +0200
commit85a3127d828260222f3232e99046523c266625d1 (patch)
tree7bb6a56d8e582d45b90774af29a9cde3528d0209
parenta52f2c77edab063734abcd1cc736367d3d1d4be5 (diff)
downloaddocs-85a3127d828260222f3232e99046523c266625d1.tar.gz
docs-85a3127d828260222f3232e99046523c266625d1.tar.bz2
docs-85a3127d828260222f3232e99046523c266625d1.zip
-fix #6966
-rw-r--r--manpages/taler-exchange-offline.1.rst15
1 files changed, 9 insertions, 6 deletions
diff --git a/manpages/taler-exchange-offline.1.rst b/manpages/taler-exchange-offline.1.rst
index f3036be..b1beaf2 100644
--- a/manpages/taler-exchange-offline.1.rst
+++ b/manpages/taler-exchange-offline.1.rst
@@ -30,12 +30,15 @@ the exchange’s long-term offline signing key and should be run in a secure
subcommands as arguments which are then processed sequentially.
The tool includes two subcommands to interact *online* with the exchange's
-REST APIs. The ``download`` subcommand downloads the future public keys from the
-running exchange. The resulting data serves as input to the ``sign`` and ``show``
-subcommands. The ``upload`` subcommand uploads the signatures created with the
-private master key to the exchange. It handles the output of all subcommands
-(except ``download``). The ``download`` and ``upload`` subcommands must naturally be
-run "online" and do not require access to the offline key.
+REST APIs. To determine how to talk to the exchange, these two subcommands
+rely on the ``BASE_URL`` configuration option from the ``[exchange]`` section
+of the configuration file. The ``download`` subcommand downloads the future
+public keys from the running exchange. The resulting data serves as input to
+the ``sign`` and ``show`` subcommands. The ``upload`` subcommand uploads the
+signatures created with the private master key to the exchange. It handles
+the output of all subcommands (except ``download``). The ``download`` and
+``upload`` subcommands must naturally be run "online" and do not require
+access to the offline key.
All other subcommands are intended to be run "offline". However, especially
when testing, it is of course possible to run the subcommands online as well.