RT-DUMP-METADATA(1)

πŸ“¦
version 5.0.10 Β· 4 versions
, in fedora 43

πŸ’Ύ rt-dump-metadata β€” the RT-DUMP-METADATA(1) page, but make it cute

okay bestie, gather round, because this one is short but it's important and I need you to not skim it πŸ’–


✨ NAME ✨

rt-dump-metadata β€” dumps configuration metadata out of an RT database, no cap


🌸 SYNOPSIS 🌸

rt-dump-metadata [--all]

that's it. that's the whole vibe. one optional flag and you're done πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

so like, rt-dump-metadata is the little tool that scoops configuration metadata out of your Request Tracker database and pours it into XML format 🫢 β€” and that XML is specifically shaped so you can feed it straight into rt-setup-database. it's giving pipeline. it's giving "one tool writes, another tool reads."

ok but fr fr, real talk: if what you actually want is to dump and load a full RT database, you should generally be reaching for the native database tools instead, plus doing whatever necessary steps UPGRADING tells you to do. this is not that tool, bestie.

and speaking of which β€” this is NOT a tool for backing up an RT database. not even a little. do not do that. 😭 also go look at initialdata if you want a more straightforward way to import data; that one's lowkey the easier path.


πŸ’… OPTIONS πŸ’…

  • --all, -a β€” run it with --all and the dump includes all the configuration metadata, the whole buffet ✨. run it without and you only get the 'local' configuration changes β€” y'know, the stuff people did manually in the web interface. just the hand-made edits, the artisanal ones πŸŽ€
  • --limit-to-privileged, -l β€” makes the dumper only dump privileged users. exclusive! πŸ‘‘
  • --skip-disabled, -s β€” ignores disabled rows in the database. if it's disabled, we don't see it, we don't know her πŸ™ˆ

that's the whole page, you ate it, I'm proud of you 🌈

perl v5.42.3 Β· 2026-07-20 Β· mwah, go dump some metadata πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from