SYNC-CONFIG(1)

πŸ“¦ version 1.3.0, in nixos 26.05, nixpkgs unstable

πŸ’… SYNC-CONFIG(1) β€” the GNU Taler one πŸŽ€

okay so bestie, this is the sync-config page from the GNU Taler manual, and it's literally the tool that reads and modifies your Sync configuration files. glamorous? no. essential? absolutely. let's get into it ✨

✨ SYNOPSIS ✨

sync-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]

πŸ¦‹ DESCRIPTION πŸ¦‹

sync-config is your little main-character tool for reading or modifying Sync configuration files. that's the whole vibe check. 🫢


🌸 the options, one by one, no skipping, i promise 🌸

  • -b BACKEND, --supported-backend=BACKEND β€” tests whether the specified BACKEND is supported by the current installation. the backend has to match the name of a plugin, i.e. "namestore_postgres" for the PostgreSQL database backend of the "NAMESTORE" service. if BACKEND is supported, sync-config returns a status code of 0 (success), otherwise 77 (unsupported). when you use this option, no other options may be specified β€” and if you do specify it with other options, sync-config returns a status code of 1 (error). it's giving "solo act only" πŸ’€
  • -c FILENAME, --config=FILENAME β€” use the configuration file FILENAME. simple as that, bestie.
  • -f, --filename β€” tries to perform expansions as if the option values represent filenames. and yes, it'll still be applied even if the option is not really a filename. no cap, it just does it anyway πŸ™ˆ
  • -F, --full β€” writes the full configuration file, not just the differences to the defaults. maximalist energy πŸ‘‘
  • -h, --help β€” prints short help on options. the classic.
  • -L LOGLEVEL, --loglevel=LOGLEVEL β€” use LOGLEVEL for logging. valid values are DEBUG, INFO, WARNING, and ERROR. pick your vibe (but like, the boring logging kind).
  • -l FILENAME, --logfile=FILENAME β€” send logging output to FILENAME. logs gotta go somewhere ✨
  • -o OPTION, --option=OPTION β€” which configuration option should be accessed or edited. required to set a value. if you don't give it, all values of a given section get printed in the format "OPTION = VALUE". so cute, so consistent πŸ’–
  • -r, --rewrite β€” write the configuration file even if nothing changed. but bestie, listen: it will remove all comments! 🚨 like, gone. highlighted and deleted. so know what you're doing.
  • -S, --list-sections β€” lists available configuration sections for use with --section. a little menu, basically πŸ“
  • -s SECTION, --section=SECTION β€” which configuration section should be accessed or edited. this one is a required option, fr fr.
  • -V VALUE, --value=VALUE β€” configuration value to store in the given section under the given option. must only be given together with -s and -o options. the trio or it doesn't happen πŸ’…
⚠️ note: changing the configuration file with -V will remove comments and may reorder sections and remove @INLINE@ directives. so your pretty annotated config? yeah. it's getting a makeover whether you asked or not 😭
  • -v, --version β€” print the GNU Taler version number. icon behavior honestly ⭐

πŸ‘€ SEE ALSO πŸ‘€

sync-dbinit(1), sync-httpd(1), sync.conf(5). go read those next, iykyk 🧚

πŸ’€ BUGS πŸ’€

report bugs by using https://bugs.taler.net or by sending electronic mail to <taler@gnu.org>. they wanna hear from you, bestie 🫢

🌈 AUTHOR 🌈

GNU Taler contributors β€” legends, every one of them πŸ‘‘

2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)


and that's the whole page, bestie! πŸ’– this was version 1.0, dated Dec 22, 2025, straight from the GNU Taler docs. slay, stay configured, and don't forget to back up before you -r πŸ¦‹βœ¨

πŸ“¦ where this page comes from