CHALLENGER-CONFIG(1)

💅 challenger-config — the GNU Taler manual, bestie edition 🎀

okay so this is CHALLENGER-CONFIG(1), a page from the GNU Taler manual (version 1.0, dated Dec 22, 2025 — yes we're serving vintage ✨). Buckle up, we're about to make config files do tricks 💖

---

🌸 NAME 🌸

challenger-config — the lil tool that lets you mess with Challenger configuration files, no cap 💅

---

✨ SYNOPSIS ✨

challenger-config [-b backend | --supported-backend=backend]
[-c filename | --config=filename] [-f | --filename] [-F | --full]
[-h | --help] [-L loglevel | --loglevel=loglevel]
[-l filename | --logfile=filename] [-o option | --option=option]
[-r | --rewrite] [-S | --list-sections] [-s section | --section=section]
[-V value | --value=value] [-v | --version]

like, that's the whole vibe in one code block 🫶

---

🦋 DESCRIPTION 🦋

challenger-config is literally your go-to for reading or modifying Challenger configuration files. icon behavior, honestly 👑

🎀 the options, one by one 🎀

• -b BACKEND | --supported-backend=BACKEND — this one runs a lil vibe check on whether BACKEND is supported by the installation you've got right now. the backend has to match the name of a plugin exactly, i.e. "namestore_postgres" for the PostgreSQL database backend of the "NAMESTORE" service. if it's supported, challenger-config bounces back with status code 0 (success, slay 💚); otherwise you get 77 (unsupported, rip 💀). when you use this option, no other options are allowed — specifying it together with other options makes challenger-config return status code 1 (error). main character energy: it wants the spotlight alone 🎤
• -c FILENAME | --config=FILENAME — use the config file FILENAME. simple as 🍓
• -f | --filename — tries to do expansions as if the option values were filenames — and heads up, it does this even if the option isn't really a filename 🙈 lowkey chaotic but go off
• -F | --full — writes out the full configuration file, not just the diffs from the defaults. full send 💅
• -h | --help — prints a short help blurb about the options. ur little pocket guide 🫶
• -L LOGLEVEL | --loglevel=LOGLEVEL — use LOGLEVEL for logging. valid values are DEBUG, INFO, WARNING, and ERROR — pick ur fighter ⭐
• -l FILENAME | --logfile=FILENAME — send the logging output to FILENAME. bye bye terminal spam 👋
• -o OPTION | --option=OPTION — which configuration option you wanna access or edit. required to set a value. if you don't give it, all values of a given section get printed in the format "OPTION = VALUE" ✨
• -r | --rewrite — writes the config file even if nothing changed. and yes — it will remove all comments! 😭 consider yourself warned, bestie
• -S | --list-sections — lists the available configuration sections, so you know what to feed to --section. it's giving menu 🎀
• -s SECTION | --section=SECTION — which configuration section you wanna access or edit. required option, no skipping it 🚨
• -V VALUE | --value=VALUE — the configuration value to store in the given section under the given option. must only be given together with -s and -o — those two are its ride-or-dies, fr fr 🫶

⚠️ Note: changing the configuration file with -V will remove comments and may reorder sections and remove @INLINE@ directives. so like. your comments are gone, your sections might shuffle, and those @INLINE@ directives? might vanish. tragic, but that's the tea 💀

• -v | --version — prints the GNU Taler version number. queen of receipts 👑

---

🔥 SEE ALSO 🔥

challenger-dbinit(1), challenger-httpd(1), challenger.conf(5) — go read those next, iykyk 💜

---

💀 BUGS 💀

found a bug? report it at https://bugs.taler.net or send electronic mail to <taler@gnu.org>. we're listening 🫶

---

🌈 AUTHOR 🌈

GNU Taler contributors — the collective 👑

---

🌸 COPYRIGHT 🌸

2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+) — legal stuff, but make it cute 🎀

---

okay that's the whole page!! and one last lil sign-off: this beautiful thing is version 1.0, dated Dec 22, 2025, straight from the GNU Taler crew — go forth and configure, bestie, you're gonna ate 💅✨🦋