rt-setup-database(8)

✨ NAME ✨

rt-setup-database — sets up the database for Request Tracker. She's the one who builds the whole foundation, no cap. 💖

---

🎀 SYNOPSIS 🎀

rt-setup-database --action ...

---

💅 OPTIONS 💅

• --action — okay so this is THE main character of the whole page. You can run several actions at once, just stack them in a comma separated list, bestie. 🫶
  • init — Initialize the database. This is literally a combo meal of multiple actions listed below: create the DB, the schema, set up acl, insert core data, and insert initial data. The whole glow-up in one go. ✨
  • upgrade — Apply all the needed schema/acl/content updates. Heads up, she will ask you for the version to upgrade from, so have that ready. 👑
  • create — Create the database. Simple. Iconic. 💅
  • drop — Drop the database. 🚨 Bestie, listen to me very carefully: this will ERASE ALL YOUR DATA. Like, gone gone. Not a vibe check you want to fail. 😭
  • schema — Initialize only the database schema. If you wanna use a local or supplementary datafile, specify it with the --datadir option below. 🦋
  • acl — Initialize only the database ACLs. Same deal: to use a local or supplementary datafile, specify it with the --datadir option below. 🌸
  • coredata — Insert data into RT's database. This data is required for the normal functioning of any RT instance, so don't skip her, she's essential. 🔥
  • insert — Insert data into RT's database. By default, she'll use RT's installation data. If you wanna use a local or supplementary datafile instead, specify it with the --datafile option below. 🍓
• --datafile — the file path of the data you wanna action on. Fr fr, this is where you point her at your data.

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

• --datadir — used to specify a path to find the local database schema and acls to be installed. She needs to know where the good stuff lives. 🌈

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

• --dba — dba's username. 👤
• --dba-password — dba's password. 🤫
• --prompt-for-dba-password — ask for the database administrator's password interactively, so it never has to sit around in plain sight. Iconic behaviour, honestly. 💜
• --skip-create — for init: skip creating the database and the user account, so we don't need administrator privileges. Lowkey the move when you're not allowed to touch the big-kid buttons. 🙈
• --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. 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 the extension making a change. Not needed for RT, since RT has a more elaborate system to track upgrades across multiple versions. She's got her own thing going on. 💫
• --upgrade-from — for upgrade: specifies the version to upgrade from, and she won't prompt for it if it appears to be a valid version. No annoying pop quiz. ✅
• --upgrade-to — for upgrade: specifies the version to upgrade to, and she won't prompt for it if it appears to be a valid version. Same energy, different direction. 🚀

---

That's the whole page, bestie — you ate. This was served to you from perl v5.38.2, dated 2023-10-29, and it's the rt-setup-database(8) page from the Request Tracker Reference. Go set up that database, you've got this. 💖✨🎀