TALER-AUDITOR-SYNC(1)

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

πŸ’… TALER-AUDITOR-SYNC πŸ’…

okay so bestie, welcome to the taler-auditor-sync manual page β€” GNU Taler edition, and honestly this one is so important, so pay attention 🫢


✨ NAME ✨

taler-auditor-sync β€” a tool to safely synchronize the auditor database πŸŽ€


🌸 SYNOPSIS 🌸

taler-auditor-sync [-s FILENAME | --source-configuration=FILENAME]
[-d FILENAME | --destination-configuration=FILENAME] [-h | --help]
[-b SIZE | --batch=SIZE] [-t | --terminate-when-synchronized]
[-v | --version] [-L LOGLEVEL | --loglevel=LOGLEVEL]

πŸ¦‹ DESCRIPTION πŸ¦‹

taler-auditor-sync is a command-line tool that synchronizes the Taler auditor's database in a safe way, pulling from a Taler exchange database. No cap, the "safe" part is the whole vibe here πŸ”₯

Here's the tea: if the exchange database violates the assumed database invariants (the ones expressed by database constraints), or if it tries to DELETE or UPDATE tables (at least the ones the auditor relies upon), then taler-auditor-sync will not replicate those changes. Instead it halts with an error πŸ’€ Periodt. It's giving protective bestie energy, and we love that for us 🫢

Its options are as follows:

  • -s FILENAME, --source-configuration=FILENAME β€” use the configuration in FILENAME to access the original (source) exchange database, so you can copy records from it πŸ“₯
  • -d FILENAME, --destination-configuration=FILENAME β€” use the configuration in FILENAME to access the target (destination) exchange database, so you can copy records to it πŸ“€
  • -t, --terminate-when-synchronized β€” the program should exit once the two databases are in sync, instead of continuously copying more records whenever the source database gets updated ✨ like, it does its job and then leaves the party, iconic
  • -h, --help β€” print short help on options πŸŽ€
  • -L LOGLEVEL, --loglevel=LOGLEVEL β€” specifies the log level to use. Accepted values are: DEBUG, INFO, WARNING, ERROR πŸ‘‘
  • -b SIZE, --batch=SIZE β€” the target number of records to copy in one transaction. Once the databases are in sync, the batch size is used to determine how long the process sleeps before trying to again synchronize the two databases 🌈 ngl, this one is not useful if -t is used πŸ™ˆ
  • -v, --version β€” print version information ⭐

🧚 SEE ALSO 🧚

taler-auditor(1), taler-auditor.conf(5), taler-exchange.conf(5), taler-exchange-dbinit(1) πŸ’œ


πŸ’€ BUGS πŸ’€

Report bugs by using https://bugs.taler.net/ or by sending electronic mail to <taler@gnu.org> πŸ“¬ fr fr, they wanna hear from you.


πŸ‘‘ AUTHOR πŸ‘‘

GNU Taler contributors 🫢


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


and that's the whole page, bestie πŸŽ€ this dropped as version 1.0 on Dec 22, 2025, brought to you by GNU Taler β€” now go sync those databases safely, iykyk πŸ’…πŸŒŸ

πŸ“¦ where this page comes from