aboutsummaryrefslogtreecommitdiff
path: root/taler-challenger-manual.rst
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2023-07-20 17:09:04 +0200
committerChristian Grothoff <christian@grothoff.org>2023-07-20 17:09:09 +0200
commit234205297e8a94bb589eff205e7396c6646c445b (patch)
tree15d2365533ec73bb89b54935722d12637b152153 /taler-challenger-manual.rst
parent0634443ccfbff2eee1d16e3ab14310612e5659ff (diff)
downloaddocs-234205297e8a94bb589eff205e7396c6646c445b.tar.gz
docs-234205297e8a94bb589eff205e7396c6646c445b.tar.bz2
docs-234205297e8a94bb589eff205e7396c6646c445b.zip
document new TOS/PP generation logic
Diffstat (limited to 'taler-challenger-manual.rst')
-rw-r--r--taler-challenger-manual.rst52
1 files changed, 3 insertions, 49 deletions
diff --git a/taler-challenger-manual.rst b/taler-challenger-manual.rst
index 1497bfed..d2c28d41 100644
--- a/taler-challenger-manual.rst
+++ b/taler-challenger-manual.rst
@@ -234,56 +234,10 @@ commands.
providers or for new types of addresses.
-Terms of Service
-----------------
-
-The exchange has an endpoint "/terms" to return the terms of service
-(in legal language) of the Challenger operator.
-
-To configure the terms of service response, there are two options
-in the ``[challenger]`` section:
-
-- ``TERMS_ETAG``: The current "Etag" to return for the terms of service.
- This value must be changed whenever the terms of service are
- updated. A common value to use would be a version number.
- Note that if you change the ``TERMS_ETAG``, you MUST also provide
- the respective files in ``TERMS_DIR`` (see below).
-- ``TERMS_DIR``: The directory that contains the terms of service.
- The files in the directory must be readable to the ``challenger-httpd``
- process.
-
-The ``TERMS_DIR`` directory structure must follow a particular layout.
-First, inside of ``TERMS_DIR``, there should be sub-directories using
-two-letter language codes like "en", "de", or "jp". Each of these
-directories would then hold translations of the current terms of
-service into the respective language. Empty directories are
-permitted in case translations are not available.
-
-Then, inside each language directory, files with the name of the
-value set as the ``TERMS_ETAG`` must be provided. The extension of
-each of the files should be typical for the respective mime type.
-The set of supported mime types is currently hard-coded in the
-exchange, and includes HTML, PDF and TXT files. If other files are
-present, Challenger may show a warning on startup.
-
-
-Example
-^^^^^^^
-
-A sample file structure for a ``TERMS_ETAG`` of "v1" would be:
-
-- TERMS_DIR/en/v1.txt
-- TERMS_DIR/en/v1.html
-- TERMS_DIR/en/v1.pdf
-- TERMS_DIR/de/v1.txt
-- TERMS_DIR/de/v1.html
-- TERMS_DIR/de/v1.pdf
-- TERMS_DIR/fr/v1.pdf
-
-If the user requests an HTML format with language preferences "fr" followed by "en",
-Challenger would return ``TERMS_DIR/en/v1.html`` lacking an HTML version in
-French.
+Legal conditions for using the service
+--------------------------------------
+.. include:: frags/legal.rst
Database Configuration
----------------------