taler-docs

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

commit fdb8d9061078ec97ea18b1a3d333531abec4a4d0
parent 874bca09e7d87567bba4a1456c0add7180ead9a2
Author: Antoine A <>
Date:   Fri, 20 Sep 2024 18:49:32 +0200

rephrase: ingest -> register

Diffstat:
Mlibeufin/nexus-manual.rst | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/libeufin/nexus-manual.rst b/libeufin/nexus-manual.rst @@ -219,7 +219,7 @@ be set up. The responsible subcommand for sending payments is ``ebics-fetch``, and its configuration is a **superset** of core-config_. On top of that, it expects the database connection string and *optionally* a frequency at which it will -downloads any new EBICS files and ingest them in the database. +downloads any new EBICS files and register them in the database. The frequency **may** be specified as @@ -238,7 +238,7 @@ command would download any unseen EBICS files: $ libeufin-nexus ebics-fetch -c "$CONFIG_FILE" --transient The ``ebics-fetch`` subcommand will always cause libeufin-nexus to download -then parse EBICS files and ingest their content statements into its local +then parse EBICS files and register their content statements into its local database. The ``--transient`` flag makes the command download and import EBICS files only @@ -265,5 +265,5 @@ the present: If the Nexus database already contains the bank account history, you might need to **reset** the database in order to have the re-downloaded transactions be - properly ingested. Be careful when resetting the database: resetting the wrong + properly registered. Be careful when resetting the database: resetting the wrong database might cause DATA LOSS!