commit f21fd227e54cdd600ce780aededde3bbb307f2ff
parent 956d46eb5540851325e1050423ab36c958b4e835
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sat, 21 Mar 2026 10:02:59 +0100
fix config file naming
Diffstat:
4 files changed, 271 insertions(+), 271 deletions(-)
diff --git a/Makefile.in b/Makefile.in
@@ -35,7 +35,7 @@ install: server tools
cp doc/man/taler-directory-httpd.1 ${DESTDIR}${mandir}/man1/
cp doc/man/taler-directory-dbinit.1 ${DESTDIR}${mandir}/man1/
cp doc/man/taler-directory.conf.5 ${DESTDIR}${mandir}/man5/
- cp taldir.conf.example ${DESTDIR}${TALER_DIRECTORY_HOME}
+ cp taler-directory.conf.example ${DESTDIR}${TALER_DIRECTORY_HOME}
uninstall:
-${RM} ${DESTDIR}${bindir}/taler-directory*
diff --git a/doc/man/directory.conf.5 b/doc/man/directory.conf.5
@@ -1,270 +0,0 @@
-.\" Man page generated from reStructuredText.
-.
-.
-.nr rst2man-indent-level 0
-.
-.de1 rstReportMargin
-\\$1 \\n[an-margin]
-level \\n[rst2man-indent-level]
-level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
--
-\\n[rst2man-indent0]
-\\n[rst2man-indent1]
-\\n[rst2man-indent2]
-..
-.de1 INDENT
-.\" .rstReportMargin pre:
-. RS \\$1
-. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
-. nr rst2man-indent-level +1
-.\" .rstReportMargin post:
-..
-.de UNINDENT
-. RE
-.\" indent \\n[an-margin]
-.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
-.nr rst2man-indent-level -1
-.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
-.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
-..
-.TH "DIRECTORY.CONF" "5" "Mar 21, 2026" "1.0" "GNU Taler"
-.SH NAME
-directory.conf \- Taler directory configuration file
-.SH DESCRIPTION
-.sp
-The configuration file is line\-oriented. Blank lines and whitespace at the
-beginning and end of a line are ignored. Comments start with \fB#\fP or \fB%\fP
-in the first column (after any beginning\-of\-line whitespace) and go to the end
-of the line.
-.sp
-The file is split into sections. Every section begins with \fB[SECTIONNAME]\fP
-and contains a number of options of the form \fBOPTION=VALUE\fP\&. There may be
-whitespace around the \fB=\fP (equal sign). Section names and options are
-\fIcase\-insensitive\fP\&.
-.sp
-The values, however, are \fIcase\-sensitive\fP\&. In particular, boolean values are
-one of \fBYES\fP or \fBNO\fP\&. Values can include whitespace by surrounding the
-entire value with \fB\(dq\fP (double quote). Note, however, that there are no
-escape characters in such strings; all characters between the double quotes
-(including other double quotes) are taken verbatim.
-.sp
-Values that represent a time duration are represented as a series
-of one or more \fBNUMBER UNIT\fP pairs, e.g. \fB60 s\fP, \fB4 weeks 1 day\fP,
-\fB5 years 2 minutes\fP\&.
-.sp
-Values that represent an amount are in the usual amount syntax:
-\fBCURRENCY:VALUE.FRACTION\fP, e.g. \fBEUR:1.50\fP\&.
-The \fBFRACTION\fP portion may extend up to 8 places.
-.sp
-Values that represent filenames can begin with a \fB/bin/sh\fP\-like variable
-reference. This can be simple, such as \fB$TMPDIR/foo\fP, or complex, such as
-\fB${TMPDIR:\-${TMP:\-/tmp}}/foo\fP\&. The variables are expanded either using
-key\-values from the \fB[PATHS]\fP section (see below) or from the environment
-(\fBgetenv()\fP). The values from \fB[PATHS]\fP take precedence over those from
-the environment. If the variable name is found in neither \fB[PATHS]\fP nor the
-environment, a warning is printed and the value is left unchanged. Variables (including those from the environment) are expanded recursively, so if \fBFOO=$BAR\fP and \fBBAR=buzz\fP then the result is \fBFOO=buzz\fP\&. Recursion is bounded to at most 128 levels to avoid undefined behavior for mutually recursive expansions like if \fBBAR=$FOO\fP in the example above.
-.sp
-The \fB[PATHS]\fP section is special in that it contains paths that can be
-referenced using \fB$\fP in other configuration values that specify
-\fIfilenames\fP\&. Note that configuration options that are not specifically
-retrieved by the application as \fIfilenames\fP will not see “$”\-expressions
-expanded. To expand \fB$\fP\-expressions when using \fBtaler\-config\fP, you must pass
-the \fB\-f\fP command\-line option.
-.sp
-The system automatically pre\-populates the \fB[PATHS]\fP section with a few values
-at run\-time (in addition to the values that are in the actual configuration
-file and automatically overwriting those values if they are present).
-These automatically generated values refer to installation properties
-from \X'tty: link https://www.gnu.org/prep/standards/html_node/Directory-Variables.html'\fI\%GNU autoconf\fP\X'tty: link'\&. The
-values are usually dependent on an \fBINSTALL_PREFIX\fP which is determined by
-the \fB\-\-prefix\fP option given to configure. The canonical values are:
-.INDENT 0.0
-.IP \(bu 2
-LIBEXECDIR = $INSTALL_PREFIX/taler/libexec/
-.IP \(bu 2
-DOCDIR = $INSTALL_PREFIX/share/doc/taler/
-.IP \(bu 2
-ICONDIR = $INSTALL_PREFIX/share/icons/
-.IP \(bu 2
-LOCALEDIR = $INSTALL_PREFIX/share/locale/
-.IP \(bu 2
-PREFIX = $INSTALL_PREFIX/
-.IP \(bu 2
-BINDIR = $INSTALL_PREFIX/bin/
-.IP \(bu 2
-LIBDIR = $INSTALL_PREFIX/lib/taler/
-.IP \(bu 2
-DATADIR = $INSTALL_PREFIX/share/taler/
-.UNINDENT
-.sp
-Note that on some platforms, the given paths may differ depending
-on how the system was compiled or installed, the above are just the
-canonical locations of the various resources. These
-automatically generated values are never written to disk.
-.sp
-Files containing default values for many of the options described below
-are installed under \fB$PREFIX/share/taler\-directory/config.d/\fP\&.
-The configuration file given with \fB\-c\fP to taler\-directory binaries
-overrides these defaults.
-.sp
-A configuration file may include another, by using the \fB@INLINE@\fP directive,
-for example, in \fBmain.conf\fP, you could write \fB@INLINE@ sub.conf\fP to
-include the entirety of \fBsub.conf\fP at that point in \fBmain.conf\fP\&.
-.sp
-Be extra careful when using \fBtaler\-directory\-config \-V VALUE\fP to change configuration
-values: it will destroy all uses of \fB@INLINE@\fP and furthermore remove all
-comments from the configuration file!
-.SS GLOBAL OPTIONS
-.sp
-The following options are from the “[directory]” section.
-.INDENT 0.0
-.TP
-.B BASE_URL
-The base URL of the service. If your service is proxied, the external base URL this service is availiable at.
-Default: \fBhttp://localhost:11000\fP
-.TP
-.B CHALLENGE_BYTES
-Number of bytes of the challenge.
-Default: \fB16\fP
-.TP
-.B VALIDATION_INITIATION_MAX
-Maximum number of pending validations for the same alias.
-Default: \fB3\fP
-.TP
-.B SOLUTION_ATTEMPT_MAX
-Maximum times a solution may be attempted for an active validation.
-Default: \fB3\fP
-.TP
-.B VALIDATION_TIMEFRAME
-Cooldown period between two successive validation requests (for the same alias).
-Default: \fB5m\fP
-.TP
-.B SOLUTION_ATTEMPT_TIMEFRAME
-Duration for which a solution must be provided for any given validation.
-Default: \fB1h\fP
-.TP
-.B VALIDATION_EXPIRATION
-Time until a pending validation expires
-Default: \fB24h\fP
-.TP
-.B VALID_PAYMENT_SYSTEM_ADDRESS_REGEX
-Defines valid payment system addresses that may be registered.
-Default: \fB\&.*\fP
-.TP
-.B MONTHLY_FEE
-Cost for registration of a single month.
-Default: \fBKUDOS:0\fP
-.TP
-.B NAVIGATION
-The navigation (header) HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/nav.html\fP
-.TP
-.B FOOTER
-The footer HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/footer.html\fP
-.TP
-.B IMPRINT_PAGE
-The imprint HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/imprint.html\fP
-.TP
-.B ABOUT_PAGE
-The about HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/about.html\fP
-.TP
-.B LANDING_PAGE
-The landing page HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/landing.html\fP
-.TP
-.B VALIDATION_LANDING
-The validation landing HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/validation_landing.html\fP
-.TP
-.B LOOKUP_RESULT_PAGE
-The lookup result HTML template file. If relative will be interpreted relative to DATADIR.
-Default: \fBweb/templates/validation_landing.html\fP
-.UNINDENT
-.sp
-The following options are from a “[directory\-<validator>]” section.
-.INDENT 0.0
-.TP
-.B ENABLED
-Is this validator enabled or disabled.
-Default: \fBfalse\fP
-.TP
-.B TYPE
-What type of validator is this. Options: \fBcommand\fP, \fBoidc\fP\&.
-Default: \fBcommand\fP
-.TP
-.B CHALLENGE_FEE
-What does the initiation of a challenge cost.
-Default: \fBKUDOS:0\fP
-.TP
-.B VALID_ALIAS_REGEX
-Defines which aliases are valid in this validator context.
-Default: empty
-.TP
-.B COMMAND
-Only when TYPE \fBcommand\fP\&. The command to execute. Must be set if TYPE is \fBcommand\fP\&.
-Default: unset
-.TP
-.B SENDER
-What should the sender of the email be. Only read by the email validator.
-Default: unset
-.TP
-.B AUTHORIZATION_ENDPOINT
-Only when TYPE \fBoidc\fP\&. The URI of the authorization endpoint.
-Default: unset
-.TP
-.B TOKEN_ENDPOINT
-Only when TYPE \fBoidc\fP\&. The URI of the token endpoint.
-Default: unset
-.TP
-.B USERINFO_ENDPOINT
-Only when TYPE \fBoidc\fP\&. The URI of the userinfo endpoint.
-Default: unset
-.TP
-.B CLIENT_ID
-Only when TYPE \fBoidc\fP\&. The OAuth client_id.
-Default: unset
-.TP
-.B CLIENT_SECRET
-Only when TYPE \fBoidc\fP\&. The OAuth client_secret.
-Default: unset
-.TP
-.B SCOPE
-Only when TYPE \fBoidc\fP\&. The OAuth scope(s) to request.
-Default: unset
-.TP
-.B ALIAS_CLAIM
-Only when TYPE \fBoidc\fP\&. The claim to read from the userinfo response. Must be equal to the alias that is being validated.
-Default: \fBsub\fP
-.UNINDENT
-.sp
-The following options are from a “[directory\-<disseminator>]” section.
-.INDENT 0.0
-.TP
-.B ENABLED
-Is this disseminator enabled or disabled.
-Default: \fBfalse\fP
-.TP
-.B ZONE
-The name (not ZEKY) of the local zone authoritative for publication of the directory.
-Default: unset
-.TP
-.B EXPIRATION
-The relative expiration time of the record sets.
-Default: \fB1d\fP
-.UNINDENT
-.SH SEE ALSO
-.sp
-taler\-directory\-dbinit(1), taler\-directory\-httpd(1), taler\-directory\-config(1).
-.SH BUGS
-.sp
-Report bugs by using \X'tty: link https://bugs.taler.net/'\fI\%https://bugs.taler.net/\fP\X'tty: link' or by sending electronic
-mail to <\X'tty: link mailto:taler@gnu.org'\fI\%taler@gnu.org\fP\X'tty: link'>.
-.SH AUTHOR
-GNU Taler contributors
-.SH COPYRIGHT
-2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)
-.\" Generated by docutils manpage writer.
-.
diff --git a/doc/man/taler-directory.conf.5 b/doc/man/taler-directory.conf.5
@@ -0,0 +1,270 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "TALER-DIRECTORY.CONF" "5" "Mar 21, 2026" "1.0" "GNU Taler"
+.SH NAME
+taler-directory.conf \- Taler directory configuration file
+.SH DESCRIPTION
+.sp
+The configuration file is line\-oriented. Blank lines and whitespace at the
+beginning and end of a line are ignored. Comments start with \fB#\fP or \fB%\fP
+in the first column (after any beginning\-of\-line whitespace) and go to the end
+of the line.
+.sp
+The file is split into sections. Every section begins with \fB[SECTIONNAME]\fP
+and contains a number of options of the form \fBOPTION=VALUE\fP\&. There may be
+whitespace around the \fB=\fP (equal sign). Section names and options are
+\fIcase\-insensitive\fP\&.
+.sp
+The values, however, are \fIcase\-sensitive\fP\&. In particular, boolean values are
+one of \fBYES\fP or \fBNO\fP\&. Values can include whitespace by surrounding the
+entire value with \fB\(dq\fP (double quote). Note, however, that there are no
+escape characters in such strings; all characters between the double quotes
+(including other double quotes) are taken verbatim.
+.sp
+Values that represent a time duration are represented as a series
+of one or more \fBNUMBER UNIT\fP pairs, e.g. \fB60 s\fP, \fB4 weeks 1 day\fP,
+\fB5 years 2 minutes\fP\&.
+.sp
+Values that represent an amount are in the usual amount syntax:
+\fBCURRENCY:VALUE.FRACTION\fP, e.g. \fBEUR:1.50\fP\&.
+The \fBFRACTION\fP portion may extend up to 8 places.
+.sp
+Values that represent filenames can begin with a \fB/bin/sh\fP\-like variable
+reference. This can be simple, such as \fB$TMPDIR/foo\fP, or complex, such as
+\fB${TMPDIR:\-${TMP:\-/tmp}}/foo\fP\&. The variables are expanded either using
+key\-values from the \fB[PATHS]\fP section (see below) or from the environment
+(\fBgetenv()\fP). The values from \fB[PATHS]\fP take precedence over those from
+the environment. If the variable name is found in neither \fB[PATHS]\fP nor the
+environment, a warning is printed and the value is left unchanged. Variables (including those from the environment) are expanded recursively, so if \fBFOO=$BAR\fP and \fBBAR=buzz\fP then the result is \fBFOO=buzz\fP\&. Recursion is bounded to at most 128 levels to avoid undefined behavior for mutually recursive expansions like if \fBBAR=$FOO\fP in the example above.
+.sp
+The \fB[PATHS]\fP section is special in that it contains paths that can be
+referenced using \fB$\fP in other configuration values that specify
+\fIfilenames\fP\&. Note that configuration options that are not specifically
+retrieved by the application as \fIfilenames\fP will not see “$”\-expressions
+expanded. To expand \fB$\fP\-expressions when using \fBtaler\-config\fP, you must pass
+the \fB\-f\fP command\-line option.
+.sp
+The system automatically pre\-populates the \fB[PATHS]\fP section with a few values
+at run\-time (in addition to the values that are in the actual configuration
+file and automatically overwriting those values if they are present).
+These automatically generated values refer to installation properties
+from \X'tty: link https://www.gnu.org/prep/standards/html_node/Directory-Variables.html'\fI\%GNU autoconf\fP\X'tty: link'\&. The
+values are usually dependent on an \fBINSTALL_PREFIX\fP which is determined by
+the \fB\-\-prefix\fP option given to configure. The canonical values are:
+.INDENT 0.0
+.IP \(bu 2
+LIBEXECDIR = $INSTALL_PREFIX/taler/libexec/
+.IP \(bu 2
+DOCDIR = $INSTALL_PREFIX/share/doc/taler/
+.IP \(bu 2
+ICONDIR = $INSTALL_PREFIX/share/icons/
+.IP \(bu 2
+LOCALEDIR = $INSTALL_PREFIX/share/locale/
+.IP \(bu 2
+PREFIX = $INSTALL_PREFIX/
+.IP \(bu 2
+BINDIR = $INSTALL_PREFIX/bin/
+.IP \(bu 2
+LIBDIR = $INSTALL_PREFIX/lib/taler/
+.IP \(bu 2
+DATADIR = $INSTALL_PREFIX/share/taler/
+.UNINDENT
+.sp
+Note that on some platforms, the given paths may differ depending
+on how the system was compiled or installed, the above are just the
+canonical locations of the various resources. These
+automatically generated values are never written to disk.
+.sp
+Files containing default values for many of the options described below
+are installed under \fB$PREFIX/share/taler\-directory/config.d/\fP\&.
+The configuration file given with \fB\-c\fP to taler\-directory binaries
+overrides these defaults.
+.sp
+A configuration file may include another, by using the \fB@INLINE@\fP directive,
+for example, in \fBmain.conf\fP, you could write \fB@INLINE@ sub.conf\fP to
+include the entirety of \fBsub.conf\fP at that point in \fBmain.conf\fP\&.
+.sp
+Be extra careful when using \fBtaler\-directory\-config \-V VALUE\fP to change configuration
+values: it will destroy all uses of \fB@INLINE@\fP and furthermore remove all
+comments from the configuration file!
+.SS GLOBAL OPTIONS
+.sp
+The following options are from the “[directory]” section.
+.INDENT 0.0
+.TP
+.B BASE_URL
+The base URL of the service. If your service is proxied, the external base URL this service is availiable at.
+Default: \fBhttp://localhost:11000\fP
+.TP
+.B CHALLENGE_BYTES
+Number of bytes of the challenge.
+Default: \fB16\fP
+.TP
+.B VALIDATION_INITIATION_MAX
+Maximum number of pending validations for the same alias.
+Default: \fB3\fP
+.TP
+.B SOLUTION_ATTEMPT_MAX
+Maximum times a solution may be attempted for an active validation.
+Default: \fB3\fP
+.TP
+.B VALIDATION_TIMEFRAME
+Cooldown period between two successive validation requests (for the same alias).
+Default: \fB5m\fP
+.TP
+.B SOLUTION_ATTEMPT_TIMEFRAME
+Duration for which a solution must be provided for any given validation.
+Default: \fB1h\fP
+.TP
+.B VALIDATION_EXPIRATION
+Time until a pending validation expires
+Default: \fB24h\fP
+.TP
+.B VALID_PAYMENT_SYSTEM_ADDRESS_REGEX
+Defines valid payment system addresses that may be registered.
+Default: \fB\&.*\fP
+.TP
+.B MONTHLY_FEE
+Cost for registration of a single month.
+Default: \fBKUDOS:0\fP
+.TP
+.B NAVIGATION
+The navigation (header) HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/nav.html\fP
+.TP
+.B FOOTER
+The footer HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/footer.html\fP
+.TP
+.B IMPRINT_PAGE
+The imprint HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/imprint.html\fP
+.TP
+.B ABOUT_PAGE
+The about HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/about.html\fP
+.TP
+.B LANDING_PAGE
+The landing page HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/landing.html\fP
+.TP
+.B VALIDATION_LANDING
+The validation landing HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/validation_landing.html\fP
+.TP
+.B LOOKUP_RESULT_PAGE
+The lookup result HTML template file. If relative will be interpreted relative to DATADIR.
+Default: \fBweb/templates/validation_landing.html\fP
+.UNINDENT
+.sp
+The following options are from a “[directory\-<validator>]” section.
+.INDENT 0.0
+.TP
+.B ENABLED
+Is this validator enabled or disabled.
+Default: \fBfalse\fP
+.TP
+.B TYPE
+What type of validator is this. Options: \fBcommand\fP, \fBoidc\fP\&.
+Default: \fBcommand\fP
+.TP
+.B CHALLENGE_FEE
+What does the initiation of a challenge cost.
+Default: \fBKUDOS:0\fP
+.TP
+.B VALID_ALIAS_REGEX
+Defines which aliases are valid in this validator context.
+Default: empty
+.TP
+.B COMMAND
+Only when TYPE \fBcommand\fP\&. The command to execute. Must be set if TYPE is \fBcommand\fP\&.
+Default: unset
+.TP
+.B SENDER
+What should the sender of the email be. Only read by the email validator.
+Default: unset
+.TP
+.B AUTHORIZATION_ENDPOINT
+Only when TYPE \fBoidc\fP\&. The URI of the authorization endpoint.
+Default: unset
+.TP
+.B TOKEN_ENDPOINT
+Only when TYPE \fBoidc\fP\&. The URI of the token endpoint.
+Default: unset
+.TP
+.B USERINFO_ENDPOINT
+Only when TYPE \fBoidc\fP\&. The URI of the userinfo endpoint.
+Default: unset
+.TP
+.B CLIENT_ID
+Only when TYPE \fBoidc\fP\&. The OAuth client_id.
+Default: unset
+.TP
+.B CLIENT_SECRET
+Only when TYPE \fBoidc\fP\&. The OAuth client_secret.
+Default: unset
+.TP
+.B SCOPE
+Only when TYPE \fBoidc\fP\&. The OAuth scope(s) to request.
+Default: unset
+.TP
+.B ALIAS_CLAIM
+Only when TYPE \fBoidc\fP\&. The claim to read from the userinfo response. Must be equal to the alias that is being validated.
+Default: \fBsub\fP
+.UNINDENT
+.sp
+The following options are from a “[directory\-<disseminator>]” section.
+.INDENT 0.0
+.TP
+.B ENABLED
+Is this disseminator enabled or disabled.
+Default: \fBfalse\fP
+.TP
+.B ZONE
+The name (not ZEKY) of the local zone authoritative for publication of the directory.
+Default: unset
+.TP
+.B EXPIRATION
+The relative expiration time of the record sets.
+Default: \fB1d\fP
+.UNINDENT
+.SH SEE ALSO
+.sp
+taler\-directory\-dbinit(1), taler\-directory\-httpd(1), taler\-directory\-config(1).
+.SH BUGS
+.sp
+Report bugs by using \X'tty: link https://bugs.taler.net/'\fI\%https://bugs.taler.net/\fP\X'tty: link' or by sending electronic
+mail to <\X'tty: link mailto:taler@gnu.org'\fI\%taler@gnu.org\fP\X'tty: link'>.
+.SH AUTHOR
+GNU Taler contributors
+.SH COPYRIGHT
+2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)
+.\" Generated by docutils manpage writer.
+.
diff --git a/taldir.conf.example b/taler-directory.conf.example
