rt-setup-database - Set up RT's database
rt-setup-database --action ... Several actions can be combined using comma separated list.
Initialize the database. This is combination of multiple actions listed below. Create DB, schema, setup acl, insert core data and initial data.
Apply all needed schema/acl/content updates (will ask for version to upgrade from)
Create the database.
Drop the database. This will ERASE ALL YOUR DATA.
Initialize only the database schema
To use a local or supplementary datafile, specify it using the '--datadir' option below.
Initialize only the database ACLs
To use a local or supplementary datafile, specify it using the '--datadir' option below.
Insert data into RT's database. This data is required for normal functioning of any RT instance.
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.
file path of the data you want to action on
e.g. --datafile /path/to/datafile
Used to specify a path to find the local database schema and acls to be installed.
e.g. --datadir /path/to/
dba's username
dba's password
Ask for the database administrator's password interactively
for 'init': skip creating the database and the user account, so we don't need administrator privileges
for 'init' and 'insert': rather than using the default administrative password for RT's "root" user, use the password in this file.
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.
current version of extension making a change. Not needed for RT since RT has a more elaborate system to track upgrades across multiple versions.
for 'upgrade': specifies the version to upgrade from, and do not prompt for it if it appears to be a valid version.
for 'upgrade': specifies the version to upgrade to, and do not prompt for it if it appears to be a valid version.