diff options
| author | MS <ms@taler.net> | 2023-11-20 09:37:59 +0100 |
|---|---|---|
| committer | MS <ms@taler.net> | 2023-11-20 09:37:59 +0100 |
| commit | e4424812add672c9f35d56818f27b704f75a14a4 (patch) | |
| tree | 8632ba684887f7d36b4724ae255e6122bf35f939 /manpages | |
| parent | 5c1cfafd11db4cab79137838022c49ebe5113bd2 (diff) | |
| download | docs-e4424812add672c9f35d56818f27b704f75a14a4.tar.gz docs-e4424812add672c9f35d56818f27b704f75a14a4.tar.bz2 docs-e4424812add672c9f35d56818f27b704f75a14a4.zip | |
indentation
Diffstat (limited to 'manpages')
| -rw-r--r-- | manpages/libeufin-nexus.conf.5.rst | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/manpages/libeufin-nexus.conf.5.rst b/manpages/libeufin-nexus.conf.5.rst index 8ec5527a..11830cc5 100644 --- a/manpages/libeufin-nexus.conf.5.rst +++ b/manpages/libeufin-nexus.conf.5.rst @@ -105,10 +105,10 @@ FREQUENCY the value *5m* causes retries to be run every five minutes. SUBMISSIONS_LOG_DIRECTORY - Optional value to define the path where the pain.001 documents would be stored - after a submission. This directory would contain several directories, each named - after the YYYY-MM-DD format. The pain.001 file would then be named in the following - schema: ``$submissionTimestampMicroseconds_requestUid_$requestUid_pain.001.xml``. + Optional value to define the path where the pain.001 documents gets stored *before* + being submitted to the bank. This directory would contain several directories, + each named after the YYYY-MM-DD format. The pain.001 file would then be named in + the following schema: ``$submissionTimestampMicroseconds_requestUid_$requestUid_pain.001.xml``. ``$requestUid`` is the same value that constitutes the pain.001 ``MsgIg`` element. In the event that one log file would be overridden, ``ebics-submit`` fails without overriding it. @@ -128,10 +128,11 @@ FREQUENCY STATEMENT_LOG_DIRECTORY Optional value to define the path where the downloaded documents would be stored - This directory would contain several directories, each named after the YYYY-MM-DD - format. The stored files would then be named in the following schema: - ``$downloadTimestampMicroseconds_$filenameAsGivenByTheBank``. In the event that - one log file would be overridden, ``ebics-fetch`` fails without overriding it. + *before* being ingested in the database. This directory would contain several + directories, each named after the YYYY-MM-DD format. The stored files would then + be named after the following schema: + ``$downloadTimestampMicroseconds_$filenameAsGivenByTheBank``. In case one log file + would be overridden, ``ebics-fetch`` fails without overriding it. Exception to this naming scheme are the HAC responses, since they do not get any filename assigned by the ZIP archive (they are sent unzipped). Their naming scheme is: ``$downloadTimestampMicroseconds_HAC_response.pain.002.xml`` |