taler-docs

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

commit be0ccfe748731518508a4e2d890382f7b68e5a8d
parent 9380147fce094c26d76a11f86ae44b064a086cdd
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 28 Oct 2023 21:40:18 +0200

document new BASE_URL optionfor #7966

Diffstat:
Mmanpages/taler-terms-generator.1.rst | 3+++
Mmanpages/taler.conf.5.rst | 3+++
2 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/manpages/taler-terms-generator.1.rst b/manpages/taler-terms-generator.1.rst @@ -47,6 +47,9 @@ Description **-l** *LANGUAGE* Add the given *LANGUAGE* to the list of translations for the current *INPUT*. *LANGUAGE* must be a two-letter language code (like "de" or "it"). This will generate or update the respective ".po" files to translate the *INPUT* terms to this *LANGUAGE*. +**-L** *LOCALE_DIR* + Specify locale/ directory where GNU gettext resources for translating the input are located. If "-l" is given, this directory is where fresh or updated ".po" files will be placed, and otherwise this directory will be scanned for translations of the ".rst" input file. + **-o** *OUTPUT* Specifies where to write the output. This should be the directory where the service expects to find the generated resources. Unless you changed the default configuration, you probably do not have to specify this value. diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst @@ -664,6 +664,9 @@ DB SERVE Should the HTTP server listen on a UNIX domain socket (set option to "unix") or on a TCP socket (set option to "tcp")? +BASE_URL + Which base URL should the merchant backend assume for itself in the protocol. Optional. If not given, the base URL will be constructed from X-Forwarded-Host, X-Forwarded-Port and X-Forwarded-Prefix headers that a reverse-proxy should be setting. + UNIXPATH Path to listen on if we "SERVE" is set to "unix".