diff options
Diffstat (limited to 'man/taler.conf.5')
| -rw-r--r-- | man/taler.conf.5 | 144 |
1 files changed, 72 insertions, 72 deletions
diff --git a/man/taler.conf.5 b/man/taler.conf.5 index 3ca1d3c4..85856dd4 100644 --- a/man/taler.conf.5 +++ b/man/taler.conf.5 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER.CONF" "5" "Mar 07, 2024" "0.9" "GNU Taler" +.TH "TALER.CONF" "5" "Apr 12, 2024" "0.9" "GNU Taler" .SH NAME taler.conf \- Taler configuration file .SH DESCRIPTION @@ -130,7 +130,7 @@ Name of the currency, e.g.\ “EUR” for Euro. .TP .B CURRENCY_ROUND_UNIT Smallest amount in this currency that can be transferred using the -underlying RTGS. For example: \(dqEUR:0.01\(dq or \(dqJPY:1\(dq. +underlying RTGS. For example: “EUR:0.01” or “JPY:1”. .UNINDENT .sp The “[PATHS]” section is special in that it contains paths that can be @@ -160,7 +160,7 @@ sockets). Usually “${TMP}/taler\-system\-runtime”. .UNINDENT .SS CURRENCY SPECIFICATIONS .sp -Sections with a name of the form “[currency\-$NAME]” (where \(dq$NAME\(dq could +Sections with a name of the form “[currency\-$NAME]” (where “$NAME” could be any unique string) are used to specify details about how currencies should be handled (and in particularly rendered) by the user interface. A detailed motivation for this section can be found in DD51. @@ -206,10 +206,10 @@ JSON map determining how to encode very large or very tiny amounts in this currency. Maps a base10 logarithm to the respective currency symbol. Must include at least an entry for 0 (currency unit). For example, use -{\(dq0\(dq:\(dq€\(dq} for Euros or \(dq{\(dq0\(dq:\(dq$\(dq} for Dollars. You could -additionally use {\(dq0\(dq:\(dq€\(dq,\(dq3\(dq:\(dqk€\(dq} to render 3000 EUR +{“0”:”€”} for Euros or “{“0”:”$”} for Dollars. You could +additionally use {“0”:”€”,”3”:”k€”} to render 3000 EUR as 3k€. For BTC a typical map would be -{\(dq0\(dq:\(dqBTC\(dq,\(dq\-3\(dq:\(dqmBTC\(dq}, informing the UI to render small +{“0”:”BTC”,”\-3”:”mBTC”}, informing the UI to render small amounts in milli\-Bitcoin (mBTC). .UNINDENT .SS EXCHANGE OPTIONS @@ -222,29 +222,29 @@ exchange tools. Plugin to use for the database, e.g.\ “postgres”. .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? +Should the HTTP server listen on a UNIX domain socket (set option to “unix”) or on a TCP socket (set option to “tcp”)? .TP .B UNIXPATH -Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. +Path to listen on if we “SERVE” is set to “unix”. .TP .B UNIXPATH_MODE -Access permission mask to use for the \(dqUNIXPATH\(dq. +Access permission mask to use for the “UNIXPATH”. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the exchange HTTP server should be bound to, e.g. \(dqlocalhost\(dq. +Hostname to which the exchange HTTP server should be bound to, e.g. “localhost”. .TP .B MASTER_PUBLIC_KEY Crockford Base32\-encoded master public key, public version of the -exchange\(aqs long\-time offline signing key. This configuration option +exchange’s long\-time offline signing key. This configuration option is also used by the \fBauditor\fP to determine the public key of the exchange which it is auditing. .TP .B AML_THRESHOLD Largest amount in this currency that can be transferred per month without -an AML staff member doing a (manual) AML check. For example: \(dqUSD:1000000\(dq. +an AML staff member doing a (manual) AML check. For example: “USD:1000000”. .TP .B KYC_AML_TRIGGER Program to run on KYC attribute data to decide whether we should immediately flag an account for AML review. Program must return 0 if a manual AML review is not needed, and non\-zero to trigger an AML review. The KYC attribute data of the new user will be passed on standard\-input. @@ -271,9 +271,9 @@ Used by the KYC logic when interacting with OAuth 2.0. .TP .B TOPLEVEL_REDIRECT_URL Where to redirect visitors that access the top\-level -\(dq/\(dq endpoint of the exchange. Should point users to +“/” endpoint of the exchange. Should point users to information about the exchange operator. -Optional setting, defaults to \(dq/terms\(dq. +Optional setting, defaults to “/terms”. .TP .B AGGREGATOR_IDLE_SLEEP_INTERVAL For how long should the taler\-exchange\-aggregator sleep when it is idle @@ -292,7 +292,7 @@ For how long should the taler\-exchange\-wirewatch sleep when it is idle before trying to look for more work? Default is 60 seconds. .TP .B AGGREGATOR_SHARD_SIZE -Which share of the range from [0,..2147483648] should be processed by one of the shards of the aggregator. Useful only for Taler exchanges with ultra high\-performance needs. When changing this value, you must stop all aggregators and run \(dqtaler\-exchange\-dbinit \-s\(dq before resuming. Default is 2147483648 (no sharding). +Which share of the range from [0,..2147483648] should be processed by one of the shards of the aggregator. Useful only for Taler exchanges with ultra high\-performance needs. When changing this value, you must stop all aggregators and run “taler\-exchange\-dbinit \-s” before resuming. Default is 2147483648 (no sharding). .TP .B SIGNKEY_LEGAL_DURATION For how long are signatures with signing keys legally valid? @@ -306,12 +306,12 @@ How many requests should the HTTP server process at most before committing suici .B TERMS_DIR Directory where the terms of service of the exchange operator can be fund. The directory must contain sub\-directories for every supported language, -using the two\-character language code in lower case, e.g. \(dqen/\(dq or \(dqfr/\(dq. +using the two\-character language code in lower case, e.g. “en/” or “fr/”. Each subdirectory must then contain files with the terms of service in various formats. The basename of the file of the current policy must be specified under \fBTERMS_ETAG\fP\&. The extension defines the mime type. -Supported extensions include \(dqhtml\(dq, \(dqhtm\(dq, \(dqtxt\(dq, \(dqpdf\(dq, \(dqjpg\(dq, \(dqjpeg\(dq, -\(dqpng\(dq and \(dqgif\(dq. For example, using a \fBTERMS_ETAG\fP of \(dq0\(dq, the structure +Supported extensions include “html”, “htm”, “txt”, “pdf”, “jpg”, “jpeg”, +“png” and “gif”. For example, using a \fBTERMS_ETAG\fP of “0”, the structure could be the following: .INDENT 7.0 .IP \(bu 2 @@ -330,7 +330,7 @@ $TERMS_DIR/de/0.txt .TP .B TERMS_ETAG Basename of the file(s) in the \fBTERMS_DIR\fP with the current terms of service. -The value is also used for the \(dqEtag\(dq in the HTTP request to control +The value is also used for the “Etag” in the HTTP request to control caching. Whenever the terms of service change, the \fBTERMS_ETAG\fP MUST also change, and old values MUST NOT be repeated. For example, the date or version number of the terms of service SHOULD be used for the Etag. If @@ -346,7 +346,7 @@ Works the same as \fBTERMS_ETAG\fP, just for the privacy policy. .UNINDENT .SS EXCHANGE KYC PROVIDER OPTIONS .sp -The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections. +The following options must be in the section “[kyc\-provider\-XXX]” sections. .INDENT 0.0 .TP .B COST @@ -363,20 +363,20 @@ List of checks performed by this provider. Space\-separated names of checks, mus .UNINDENT .SS EXCHANGE KYC OAUTH2 OPTIONS .sp -The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = oauth2\(dq. +The following options must be in the section “[kyc\-provider\-XXX]” sections with “LOGIC = oauth2”. .INDENT 0.0 .TP .B KYC_OAUTH2_VALIDITY -Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. +Duration (e.g. “12 months”) of the validity of the performed KYC check. Can be “forever”. .TP .B KYC_OAUTH2_AUTHORIZE_URL -URL of the OAuth2 endpoint to be used for KYC checks. The authorize URL is where the exchange will redirect the client to begin the authorization process. Example: \(dq\fI\%http://localhost:8888/oauth/v2/authorize\fP\(dq. To use the plugin in combination with the Challenger service\(aqs \fB/setup\fP step, append \(dq#setup\(dq, thus \(dq\fI\%https://challenger.example.com/authorize#setup\fP\(dq. Here, \(dq#setup\(dq is not a fragment but merely a hint to the logic to determine the full authorization URL via the \fB/setup/$CLIENT_ID\fP handler. +URL of the OAuth2 endpoint to be used for KYC checks. The authorize URL is where the exchange will redirect the client to begin the authorization process. Example: “\fI\%http://localhost:8888/oauth/v2/authorize\fP”. To use the plugin in combination with the Challenger service’s \fB/setup\fP step, append “#setup”, thus “\fI\%https://challenger.example.com/authorize#setup\fP”. Here, “#setup” is not a fragment but merely a hint to the logic to determine the full authorization URL via the \fB/setup/$CLIENT_ID\fP handler. .TP .B KYC_OAUTH2_TOKEN_URL -URL of the OAuth2 endpoint to be used for KYC checks. This is where the server will ultimately send the authorization token from the client and obtain its access token (which currently must be a \(dqbearer\(dq token). Example: \(dq\fI\%http://localhost:8888/oauth/v2/token\fP\(dq (or just \(dq/token\(dq) +URL of the OAuth2 endpoint to be used for KYC checks. This is where the server will ultimately send the authorization token from the client and obtain its access token (which currently must be a “bearer” token). Example: “\fI\%http://localhost:8888/oauth/v2/token\fP” (or just “/token”) .TP .B KYC_OAUTH2_INFO_URL -URL of the OAuth2\-protected resource endpoint, where the OAuth 2.0 token can be used to download information about the user that has undergone the KYC process. The exchange will use the access token obtained from the KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. Example: \(dq\fI\%http://localhost:8888/api/user/me\fP\(dq or \(dq\fI\%http://localhost:8888/oauth/v2/info\fP\(dq +URL of the OAuth2\-protected resource endpoint, where the OAuth 2.0 token can be used to download information about the user that has undergone the KYC process. The exchange will use the access token obtained from the KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. Example: “\fI\%http://localhost:8888/api/user/me\fP” or “\fI\%http://localhost:8888/oauth/v2/info\fP” .TP .B KYC_OAUTH2_CLIENT_ID Client ID of the exchange when it talks to the KYC OAuth2 endpoint. @@ -385,7 +385,7 @@ Client ID of the exchange when it talks to the KYC OAuth2 endpoint. Client secret of the exchange to use when talking to the KYC Oauth2 endpoint. .TP .B KYC_OAUTH2_POST_URL -URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. Example: \(dq\fI\%http://example.com/thank\-you\fP\(dq +URL to which the exchange will redirect the client’s browser after successful authorization/login for the KYC process. Example: “\fI\%http://example.com/thank\-you\fP” .TP .B KYC_OAUTH2_CONVERTER_HELPER Helper to convert JSON with KYC data returned by the OAuth2.0 info endpoint into GNU Taler internal format. Specific to the OAuth 2.0 provider. @@ -394,15 +394,15 @@ Helper to convert JSON with KYC data returned by the OAuth2.0 info endpoint into Set to YES to allow error responses to include potentially sensitive private information (such as full responses from the OAuth 2.0 server) that might aid in debugging -problems. Should be set to \(dqNO\(dq in production. +problems. Should be set to “NO” in production. .UNINDENT .SS EXCHANGE KYC KYCAID OPTIONS .sp -The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = kycaid\(dq. +The following options must be in the section “[kyc\-provider\-XXX]” sections with “LOGIC = kycaid”. .INDENT 0.0 .TP .B KYC_KYCAID_VALIDITY -Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. +Duration (e.g. “12 months”) of the validity of the performed KYC check. Can be “forever”. .TP .B KYC_KYCAID_AUTH_TOKEN Authentication token to access the KYC service. @@ -411,15 +411,15 @@ Authentication token to access the KYC service. ID that specifies the form to use for the KYC process. .TP .B KYC_KYCAID_POST_URL -URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. +URL to which the exchange will redirect the client’s browser after successful authorization/login for the KYC process. .UNINDENT .SS EXCHANGE KYC PERSONA OPTIONS .sp -The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = persona\(dq. +The following options must be in the section “[kyc\-provider\-XXX]” sections with “LOGIC = persona”. .INDENT 0.0 .TP .B KYC_PERSONA_VALIDITY -Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. +Duration (e.g. “12 months”) of the validity of the performed KYC check. Can be “forever”. .TP .B KYC_PERSONA_AUTH_TOKEN Authentication token to access the KYC service. @@ -431,17 +431,17 @@ Salt value to use for request idempotency. Optional, generated at random per pro Subdomain to use under Persona. .TP .B KYC_PERSONA_CONVERTER_HELPER -Helper to convert JSON with KYC data returned by Persona into GNU Taler internal format. Should probably always be set to \(dqtaler\-exchange\-kyc\-persona\-converter.sh\(dq. +Helper to convert JSON with KYC data returned by Persona into GNU Taler internal format. Should probably always be set to “taler\-exchange\-kyc\-persona\-converter.sh”. .TP .B KYC_PERSONA_POST_URL -URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. +URL to which the exchange will redirect the client’s browser after successful authorization/login for the KYC process. .TP .B KYC_PERSONA_TEMPLATE_ID ID of the Persona template to use. .UNINDENT .SS EXCHANGE KYC PERSONA GLOBAL OPTIONS .sp -The following option must be in the section \(dq[kyclogic\-persona]\(dq. +The following option must be in the section “[kyclogic\-persona]”. .INDENT 0.0 .TP .B WEBHOOK_AUTH_TOKEN @@ -453,7 +453,7 @@ The functionality of the exchange can be extended by extensions. Those are shared libraries which implement the extension\-API of the exchange and are located under \fB$LIBDIR\fP, starting with prefix \fBlibtaler_extension_\fP\&. Each extension can be enabled by adding a dedicated section -\(dq[exchange\-extension\-<extensionname>]\(dq and the following option: +“[exchange\-extension\-<extensionname>]” and the following option: .INDENT 0.0 .TP .B ENABLED @@ -463,7 +463,7 @@ options might be set in the same section. .SS EXCHANGE EXTENSION FOR AGE RESTRICTION .sp The extension for age restriction support can be enabled by adding a section -\(dq[exchange\-extension\-age_restriction]\(dq with the following options: +“[exchange\-extension\-age_restriction]” with the following options: .INDENT 0.0 .TP .B ENABLE @@ -472,8 +472,8 @@ Must be set to \fBYES\fP in order to activate the extension. .B AGE_GROUPS A colon\-seperated string of increasing non\-negative integers, defining the buckets of age groups supported by the exchange. Each integer marks the -beginning of the next age group. The zero\(aqth age group implicitly starts -with 0. For example, the string \(dq10:18\(dq would define three age groups: +beginning of the next age group. The zero’th age group implicitly starts +with 0. For example, the string “10:18” would define three age groups: .INDENT 7.0 .INDENT 3.5 .INDENT 0.0 @@ -487,7 +487,7 @@ Group 2: ages 18 and above .UNINDENT .UNINDENT .sp -If not provided, the default value is \(dq8:10:12:14:16:18:21\(dq. +If not provided, the default value is “8:10:12:14:16:18:21”. .UNINDENT .sp \fBNote\fP: Age restriction is bound to specific denominations and must be @@ -496,7 +496,7 @@ the option \fBAGE_RESTRICTED = YES\fP, see \fI\%EXCHANGE COIN OPTIONS\fP\&. Howe age groups are defined globally for all denominations. .SS EXCHANGE OFFLINE SIGNING OPTIONS .sp -The following options must be in the section \(dq[exchange\-offline]\(dq. +The following options must be in the section “[exchange\-offline]”. .INDENT 0.0 .TP .B MASTER_PRIV_FILE @@ -523,7 +523,7 @@ this option will also be ignored. .UNINDENT .SS EXCHANGE RSA CRYPTO HELPER OPTIONS .sp -The following options must be in the section \(dq[taler\-exchange\-secmod\-rsa]\(dq. +The following options must be in the section “[taler\-exchange\-secmod\-rsa]”. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -550,7 +550,7 @@ Note that the \fBtaler\-exchange\-secmod\-rsa\fP also evaluates the \fB[coin_*]\ configuration sections described below. .SS EXCHANGE CS CRYPTO HELPER OPTIONS .sp -The following options must be in the section \(dq[taler\-exchange\-secmod\-cs]\(dq. +The following options must be in the section “[taler\-exchange\-secmod\-cs]”. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -577,7 +577,7 @@ Note that the \fBtaler\-exchange\-secmod\-cs\fP also evaluates the \fB[coin_*]\f configuration sections described below. .SS EXCHANGE EDDSA CRYPTO HELPER OPTIONS .sp -The following options must be in the section \(dq[taler\-exchange\-secmod\-eddsa]\(dq. +The following options must be in the section “[taler\-exchange\-secmod\-eddsa]”. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -604,7 +604,7 @@ On which path should the security module listen for signing requests? .UNINDENT .SS EXCHANGE DATABASE OPTIONS .sp -The following options must be in the section \(dq[exchangedb]\(dq. +The following options must be in the section “[exchangedb]”. .INDENT 0.0 .TP .B IDLE_RESERVE_EXPIRATION_TIME @@ -665,7 +665,7 @@ URL of the wire gateway. Typically of the form \fBhttps://$HOSTNAME[:$PORT]/taler\-wire\-gateway/$USERNAME/\fP where $HOSTNAME is the hostname of the system running the bank (such as the Taler Python bank or the Nexus) and \fB$USERNAME\fP is -the username of the exchange\(aqs bank account (usually matching +the username of the exchange’s bank account (usually matching the \fBUSERNAME\fP option used for authentication). Example: \fBhttps://bank.demo.taler.net/taler\-wire\-gateway/Exchange/\fP\&. .TP @@ -720,12 +720,12 @@ What fee is charged for refunds? When a coin is refunded, the deposit fee is returned. Instead, the refund fee is charged to the customer. .TP .B CIPHER -What cryptosystem should be used? Must be set to either \(dqCS\(dq or \(dqRSA\(dq. +What cryptosystem should be used? Must be set to either “CS” or “RSA”. The respective crypto\-helper will then generate the keys for this denomination. .TP .B RSA_KEYSIZE -What is the RSA keysize modulos (in bits)? Only used if \(dqCIPHER=RSA\(dq. +What is the RSA keysize modulos (in bits)? Only used if “CIPHER=RSA”. .TP .B AGE_RESTRICTED Setting this option to \fBYES\fP marks the denomination as age restricted @@ -742,22 +742,22 @@ merchant backend. Plugin to use for the database, e.g._“postgres”. .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? +Should the HTTP server listen on a UNIX domain socket (set option to “unix”) or on a TCP socket (set option to “tcp”)? .TP .B 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. .TP .B UNIXPATH -Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. +Path to listen on if we “SERVE” is set to “unix”. .TP .B UNIXPATH_MODE -Access permission mask to use for the \(dqUNIXPATH\(dq. +Access permission mask to use for the “UNIXPATH”. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the merchant HTTP server should be bound to, e.g. \(dqlocalhost\(dq. +Hostname to which the merchant HTTP server should be bound to, e.g. “localhost”. .TP .B LEGAL_PRESERVATION How long do we keep data in the database for tax audits after the @@ -792,7 +792,7 @@ Base URL of the exchange, e.g.\ “\fI\%https://exchange.demo.taler.net/\fP” .TP .B MASTER_KEY Crockford Base32 encoded master public key, public version of the -exchange\(aqs long\-time offline signing key. Can be omitted, in that +exchange’s long\-time offline signing key. Can be omitted, in that case the exchange will NOT be trusted unless it is audited by a known auditor. Omitting \fBMASTER_KEY\fP can be useful if we do not trust the exchange @@ -828,19 +828,19 @@ processes that do not have access to the (offline) auditor private key file. Base URL of the auditor, e.g.\ “\fI\%https://auditor.demo.taler.net/\fP” .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? +Should the HTTP server listen on a UNIX domain socket (set option to “unix”) or on a TCP socket (set option to “tcp”)? .TP .B UNIXPATH -Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. +Path to listen on if we “SERVE” is set to “unix”. .TP .B UNIXPATH_MODE -Access permission mask to use for the \(dqUNIXPATH\(dq. +Access permission mask to use for the “UNIXPATH”. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the merchant HTTP server should be bound to, e.g. \(dqlocalhost\(dq. +Hostname to which the merchant HTTP server should be bound to, e.g. “localhost”. .UNINDENT .SS AUDITOR POSTGRES BACKEND DATABASE OPTIONS .sp @@ -849,12 +849,12 @@ The following options must be in section “[auditordb\-postgres]” if the .INDENT 0.0 .TP .B CONFIG -How to access the database, e.g.\ \(dqpostgres:///taler\(dq to use the -\(dqtaler\(dq database. Testcases use “talercheck”. +How to access the database, e.g.\ “postgres:///taler” to use the +“taler” database. Testcases use “talercheck”. .UNINDENT .SS Bank Options .sp -The following options must be in section \(dq[bank]\(dq for the taler\-fakebank\-run(1) command. They are not used by the exchange or LibEuFin! +The following options must be in section “[bank]” for the taler\-fakebank\-run(1) command. They are not used by the exchange or LibEuFin! .INDENT 0.0 .TP .B HTTP_PORT @@ -878,28 +878,28 @@ Program to run while not vending, possibly useful to show advertisements on the ESSID to advertise to wallets for use as an open WiFi to make payments (optional). .TP .B FULFILLMENT_MSG -Message shown to users by their wallets upon successful payment. If \(dq${PRODUCT_DESCRIPTION}\(dq appears in the message, it will be replaced with the description of the product that was sold. +Message shown to users by their wallets upon successful payment. If “${PRODUCT_DESCRIPTION}” appears in the message, it will be replaced with the description of the product that was sold. .TP .B BACKEND_BASE_URL Base URL (possibly including instance) for the Taler merchant backend used to process payments. .TP .B BACKEND_AUTHORIZATION -Full HTTP \(dqAuthorization\(dq header (usually with a Bearer token) to be send to the merchant backend for authorization of requests. Mandatory. +Full HTTP “Authorization” header (usually with a Bearer token) to be send to the merchant backend for authorization of requests. Mandatory. .TP .B FRAMEBUFFER_BACKLIGHT -Name of the file used to control brightness of the display. Optional. Defaults to \(dq/sys/class/backlight/soc:backlight/brightness\(dq if not given. +Name of the file used to control brightness of the display. Optional. Defaults to “/sys/class/backlight/soc:backlight/brightness” if not given. .TP .B FRAMEBUFFER_DEVICE -Name of the framebuffer device to use. Defaults to \(dq/dev/fb1\(dq if not given. +Name of the framebuffer device to use. Defaults to “/dev/fb1” if not given. .TP .B UART_DEVICE -Name of the UART device to use. Defaults to \(dq/dev/ttyAMA0\(dq if not given. +Name of the UART device to use. Defaults to “/dev/ttyAMA0” if not given. .TP .B FAIL_COMMAND Command to run to display a failure to the user. If not given, errors will not be properly shown. .UNINDENT .sp -Each products being sold must be configured in a section where the name starts with \(dqproduct\-\(dq. +Each products being sold must be configured in a section where the name starts with “product\-“. In these sections, the options that must be provided are: .INDENT 0.0 .TP @@ -907,22 +907,22 @@ In these sections, the options that must be provided are: Number identifying the slot in the vending machine that corresponds to this product. .TP .B INSTANCE -Instance to use for the payment. Optional. If not given, the BACKEND_BASE_URL from \(dq[taler\-mdb]\(dq will be used. +Instance to use for the payment. Optional. If not given, the BACKEND_BASE_URL from “[taler\-mdb]” will be used. .TP .B BACKEND_AUTHORIZATION -Full HTTP \(dqAuthorization\(dq header (usually with a Bearer token) to be send to the merchant backend for authorization of requests. Optional, will use global BACKEND_AUTHORIZATION setting from \(dq[taler\-mdb]\(dq if missing. +Full HTTP “Authorization” header (usually with a Bearer token) to be send to the merchant backend for authorization of requests. Optional, will use global BACKEND_AUTHORIZATION setting from “[taler\-mdb]” if missing. .TP .B DESCRIPTION -Human\-readable description of the product. Use \(dqempty\(dq if the product is known to be sold out (only effective if selling out is enabled via command\-line). +Human\-readable description of the product. Use “empty” if the product is known to be sold out (only effective if selling out is enabled via command\-line). .TP .B PRICE -Actual price of the product, as a Taler amount (\(dq$CURRENCY:$VALUE.$FRACTION\(dq). +Actual price of the product, as a Taler amount (“$CURRENCY:$VALUE.$FRACTION”). .TP .B KEY Key used to select the product from the console during testing. Optional. .TP .B THUMBNAIL -Name of a filename with a preview image of the product to be given to the wallet. Optional. Only \(dq.png\(dq, \(dq.jpg\(dq, \(dq.jpeg\(dq and \(dq.svg\(dq are supported at this time. +Name of a filename with a preview image of the product to be given to the wallet. Optional. Only “.png”, “.jpg”, “.jpeg” and “.svg” are supported at this time. .UNINDENT .SH SEE ALSO .sp @@ -935,6 +935,6 @@ mail to <\fI\%taler@gnu.org\fP>. .SH AUTHOR GNU Taler contributors .SH COPYRIGHT -2014-2022 Taler Systems SA (GPLv3+ or GFDL 1.3+) +2014-2024 Taler Systems SA (GPLv3+ or GFDL 1.3+) .\" Generated by docutils manpage writer. . |