RT-SETUP-DATABASE(1)

👑 RT-SETUP-DATABASE 👑

okay bestie, so this is the manual page for rt-setup-database — the lil script that builds out RT's database from absolutely nothing, or upgrades it, or (if you're feeling chaotic) nukes it entirely. It lives in the User Contributed Perl Documentation corner of the man-verse, and it is, frankly, iconic. 💅

---

✨ NAME ✨

rt-setup-database — Set up RT's database 🎀

---

🌈 SYNOPSIS 🌈

rt-setup-database --action ...

that's it. that's the whole vibe. you hand it an action and it goes. 🦋

---

💖 OPTIONS 💖

🫶 action

the main character of this whole page ngl

Several actions can be combined using comma separated list. yep, you can stack them — just comma-separate and let it cook. 🔥

• init — Initialize the database. This is combination of multiple actions listed below. Create DB, schema, setup ACL, insert core data and initial data. it's literally the everything-bagel of actions. 🥯
• upgrade — Apply all needed schema/ACL/content updates (will ask for version to upgrade from). it'll slide into your DMs asking which version you're upgrading from, so be ready.
• create — Create the database. just... make it. boom.
• drop — Drop the database. This will ERASE ALL YOUR DATA. not a drill bestie. it's giving irreversible. 💀 seriously, back that thing up first, i'm begging.
• schema — Initialize only the database schema.
  • To use a local or supplementary datafile, specify it using the --datadir option below.
• acl — Initialize only the database ACLs
  • To use a local or supplementary datafile, specify it using the --datadir option below.
• coredata — Insert data into RT's database. This data is required for normal functioning of any RT instance. no coredata = no working RT, so like, don't skip this one. 🙈
• insert — Insert data into RT's database. By default, will use RT's installation data. To use a local or supplementary datafile, specify it using 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

DBA's username

💜 dba-password

DBA's password

💜 prompt-for-dba-password

Ask for the database administrator's (DBA) password interactively — aka it'll ask you nicely instead of you pasting secrets into your shell history. living that secure life, we love to see it. 🎀

⭐ skip-create

for init: skip creating the database and the user account, so we don't need administrator privileges. perfect for when you don't have the admin keys to the kingdom. 👑

🔥 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. it's basically your name tag at the DB party. 🫶

🦋 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 said "i got this handled myself actually" ✨

🧚 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.

---

tiny reminder bestie: drop is permanent. the data does not come back. the vibe check does not save you here. 😭

---

and that's the whole page!! no cap. this gem was written by perl, version perl v5.42.3, dated 2026-07-20, and it's filed under RT-SETUP-DATABASE(1) in the User Contributed Perl Documentation section. go set up that database, you absolute icon. 🌟💅