SYNC-CONFIG(1)
π 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 πΈ
-bBACKEND,--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-configreturns a status code of0(success), otherwise77(unsupported). when you use this option, no other options may be specified β and if you do specify it with other options,sync-configreturns a status code of1(error). it's giving "solo act only" π-cFILENAME,--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.-LLOGLEVEL,--loglevel=LOGLEVEL β use LOGLEVEL for logging. valid values areDEBUG,INFO,WARNING, andERROR. pick your vibe (but like, the boring logging kind).-lFILENAME,--logfile=FILENAME β send logging output to FILENAME. logs gotta go somewhere β¨-oOPTION,--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 π-sSECTION,--section=SECTION β which configuration section should be accessed or edited. this one is a required option, fr fr.-VVALUE,--value=VALUE β configuration value to store in the given section under the given option. must only be given together with-sand-ooptions. the trio or it doesn't happen π
β οΈ note: changing the configuration file with-Vwill 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 π
π COPYRIGHT π
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
- nixos 26.05: taler-sync 1.3.0
- nixpkgs unstable: taler-sync 1.3.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms