taler-docs

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

commit b231c3dcc34c1d7997bfb8c00acb217738342fca
parent df0174cfd3c26a36eae59a99931199dfd9fcaa8b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun,  8 Aug 2021 22:32:20 +0200

-generate taler-auditor-sync man page

Diffstat:
Mconf.py | 2++
Mmanpages/taler.conf.5.rst | 6+++++-
2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/conf.py b/conf.py @@ -280,6 +280,8 @@ man_pages = [ 1), ("manpages/taler-auditor-dbinit.1", "taler-auditor-dbinit", "setup auditor database", "GNU Taler contributors", 1), + ("manpages/taler-auditor-sync.1", "taler-auditor-sync", + "tool to safely synchronize auditor database", "GNU Taler contributors", 1), ("manpages/taler-auditor-httpd.1", "taler-auditor-httpd", "HTTP server providing a RESTful API to access a Taler auditor", "GNU Taler contributors", 1), diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst @@ -52,7 +52,11 @@ 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``. -.. TODO: Document ‘taler-config -V’ in light of ‘@INLINE@’ in taler-config(1). + +Be extra careful when using ``taler-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 --------------