commit 8d2d0cf39df57a166a7476b1d4cb78e7b5a565cf
parent b711d0c657b19f16d1a576b0ffeaadabd84198cb
Author: Christian Grothoff <christian@grothoff.org>
Date: Thu, 11 Apr 2024 22:49:52 +0200
remove dead manpages
Diffstat:
2 files changed, 1 insertion(+), 8 deletions(-)
diff --git a/conf.py b/conf.py
@@ -729,13 +729,6 @@ man_pages = [
1,
),
(
- "manpages/libeufin-sandbox.1",
- "libeufin-sandbox",
- "simulate core banking system with EBICS access to bank accounts",
- "GNU Taler contributors",
- 1,
- ),
- (
"manpages/libeufin-nexus.1",
"libeufin-nexus",
"service to interface to various bank access APIs",
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
@@ -2319,7 +2319,7 @@ banking protocol standard. It uses a Postgres database to persist data and is
thus much slower than fakebank. If your GNU Taler deployment uses libeufin in
production, it likely makes sense to benchmark with libeufin. When using the
fakebank, ``taler-unified-setup.sh`` must be started with the ``-ns`` options
-(starting libeufin-nexus and libeufin-sandbox) and be told to use the right
+(starting libeufin-nexus and libeufin-bank) and be told to use the right
exchange bank account from the configuration files via ``-u
exchange-account-2``. Note that ``taler-unified-setup.sh`` currently cannot
reset a libeufin database, and also will not run if the database is already
