rt-setup-database(8)

💖 NAME 💖

rt-setup-database — bestie, this is the tool that sets up the database for Request Tracker. That's it, that's the job, and it's lowkey the most important first step of your whole RT era. It's rt-setup-database(8) from the Request Tracker Reference, and yes she's an 8 — section 8, admin commands, main character energy only. 👑

---

✨ SYNOPSIS ✨

rt-setup-database --action ...

---

🎀 OPTIONS 🎀

• action — the thing you actually want to do. Not me being vague, okay, it's literally the whole vibe of the command. And plot twist: you can stack several actions together with a comma separated list, no cap. Here's the menu:
  • init — initialize the database. This one is a combo move, it's a combination of multiple actions listed below, so it does: create DB, schema, setup ACL, insert core data and initial data. Basically the whole glow-up in one go. 🦋
  • upgrade — apply all needed schema/ACL/content updates. Heads up bestie, it will ask for the version to upgrade from, so have that number ready. ✨
  • create — create the database. Simple. Iconic. 🫶
  • drop — drop the database. And girl, I need you to hear me: this will ERASE ALL YOUR DATA. Not some of it. ALL of it. 💀
  • schema — initialize only the database schema.
    • Wanna use a local or supplementary datafile instead? Point at it with the --datadir option below. 📁
  • acl — initialize only the database ACLs.
    • Same deal, if you want a local or supplementary datafile, hit up the --datadir option below. 📁
  • coredata — insert data into RT's database. And just so you know, this data is required for normal functioning of any RT instance — it's not optional garnish, it's the whole meal. 🌸
  • insert — insert data into RT's database. By default it'll use RT's installation data. But if you want a local or supplementary datafile, specify it with the --datafile option below. 🌈
• datafile — file path of the data you want to action on.

e.g. "--datafile /path/to/datafile"

• datadir — used to specify a path to find the local database schema and ACLs to be installed.

e.g. "--datadir /path/to/"

• dba — the DBA's username. That's database administrator, if you were wondering. 🧚
• dba-password — the DBA's password. 🤫
• prompt-for-dba-password — ask for the database administrator's (DBA) password interactively, so you're typing it in live instead of parking it on the command line.
• skip-create — for 'init': skip creating the database and the user account, so we don't need administrator privileges. Very "I don't have the keys to the building but I still got in" of you. 💅
• root-password-file — for 'init' and 'insert': rather than using the default administrative password for RT's "root" user, use the password in this file. 🔐
• package — the name of the entity performing a create or upgrade. It's used for logging changes in the DB. Defaults to RT; otherwise it should be the fully qualified package name of the extension or plugin making changes to the DB. 🏷️
• ext-version — current version of extension making a change. Not needed for RT, since RT has a more elaborate system to track upgrades across multiple versions. RT is just built different, fr fr. 👑
• upgrade-from — for 'upgrade': specifies the version to upgrade from, and do not prompt for it if it appears to be a valid version. ⭐
• upgrade-to — for 'upgrade': specifies the version to upgrade to, and do not prompt for it if it appears to be a valid version. ⭐

---

okay that's the whole page, go set up that database bestie 💖✨

this was rt-setup-database(8) brought to you by perl v5.40.1, dated 2026-06-21 — Request Tracker Reference, periodt. 🎀