blob: 6081a89393ee16b2529805f64db4870906f9384f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
challenger.conf(5)
##################
.. only:: html
Name
====
**challenger.conf** - Challenger configuration file
Description
===========
.. include:: ../frags/common-conf-syntax.rst
Files containing default values for many of the options described below
are installed under ``$PREFIX/share/challenger/config.d/``.
The configuration file given with **-c** to Challenger binaries
overrides these defaults.
A configuration file may include another, by using the ``@INLINE@`` directive,
for example, in ``main.conf``, you could write ``@INLINE@ sub.conf`` to
include the entirety of ``sub.conf`` at that point in ``main.conf``.
Be extra careful when using ``challenger-config -V VALUE`` to change configuration
values: it will destroy all uses of ``@INLINE@`` and furthermore remove all
comments from the configuration file!
GLOBAL OPTIONS
--------------
The following options are from the “[challenger]” section.
This is normally the only section in a challenger.conf file.
SERVE
This can either be ``tcp`` or ``unix``.
PORT
Port on which the HTTP server listens, e.g. 9967.
Only used if ``SERVE`` is ``tcp``.
BIND_TO
Which IP address should we bind to? E.g. ``127.0.0.1`` or ``::1``
for loopback. Can also be given as a hostname. We will bind to
the wildcard (dual-stack) if left empty.
Only used if ``SERVE`` is ``tcp``.
UNIXPATH
Which unix domain path should we bind to?
Only used if ``SERVE`` is ``unix``.
UNIXPATH_MODE = 660
What should be the file access permissions for ``UNIXPATH``?
Only used if ``SERVE`` is ``unix``.
DB
Plugin to use for the database, e.g. “postgres”.
SEE ALSO
========
challenger-dbinit(1), challenger-httpd(1), challenger-config(1).
BUGS
====
Report bugs by using https://bugs.taler.net/ or by sending electronic
mail to <taler@gnu.org>.
|
