BSD Ports

www/rt60 6.0.4 DragonFly

Industrial-grade ticketing system written in Perl

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
GPLv2
Categories
www
Package size
9017.2 KiB, 43067.9 KiB installed

Description

RT is a battle-tested issue tracking system which thousands of organizations use for bug tracking, help desk ticketing, customer service, workflow processes, change management, network operations, youth counselling and even more. Organizations around the world have been running smoothly thanks to RT for over 10 years.

In the other systems

The newest version among them is 6.0.4, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
DragonFlywww/rt606.0.4 newestnone known-[email protected]-
FreeBSDwww/rt606.0.4 newestnone known-[email protected]2026-11-04
HardenedBSDwww/rt606.0.3_1 behind since 2026-11-04no data-[email protected]-
GhostBSDwww/rt606.0.3_1 behind since 2026-11-04no data-[email protected]-

Version history 1

  1. 6.0.4

Upstream's version as each commit to the port's Makefile set it, or as this site first saw it in the system's packages; the tree's own revisions are not versions here.

Install

Binary package:

pkg install rt60

From DPorts:

cd /usr/dports/www/rt60 && make install clean

Dependency graph

Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.

Dependencies

Run dependencies 106

The first 100 are listed.

No port depends on this one.

Related ports

The same software or family in DragonFly: one homepage, or one name but for a version or a variant.

Configuration

No options to configure.

Service scripts
none

Message after installing

To initialize RT's database:

$ sudo perl rt-setup-database --action init --dba dba --dba-password X

To clear a previously created RT database:

$ sudo perl rt-setup-database --action drop --dba dba --dba-password X

To complete the installation of this port, please follow these steps:

1. Edit /usr/local/etc/rt60/RT_SiteConfig.pm, by referring to
   the default config file (/usr/local/etc/rt60/RT_Config.pm).
2. Configure the email and web gateways.  Please refer to
   'SETTING UP THE MAIL GATEWAY' in /usr/local/share/doc/rt60/README
3. Restart Apache or whichever web delivery mechanism you selected..
4. Do remember to *CHANGE* the root's password for the web interface.
   The default is "password" (without the quotes.)
5. Configure RT per the instructions at
   https://docs.bestpractical.com/rt/6.0.0/index.html

RT does not work with perl taint mode (-T) you must disable it.
Note, some other ports like devel/bugzilla have you add this to your
httpd.conf.  This isn't actually a flaw of RT, but of a subset of the
CPAN modules that RT uses.

If you're upgrading RT then it is worth reading the UPGRADING document
at this point. Some extension you're using may have been integrated
into core. It's recommended to use new clean directory when you're
upgrading to new release (for example from 4.0.x to 4.2.x).

To upgrade your database schema, preserving ticket history:

1. Backup your RT database.
2. If upgrading to a new major release, create a new database named
   rt6 with appropriate rights for the rt_user and reload your
   database backup into it.
3. Run:

# /usr/local/sbin/rt-setup-database \
     --datadir /usr/local/share/doc/rt60/upgrade \
     --action upgrade --prompt-for-dba-password

and answer the prompts.

A new configuration option $SecretKey has been added. This key is used
as keying material for cryptographic operations such as MFA-reset tokens
and TOTP secret encryption. When empty (the default), RT falls back to
$DatabasePassword. We recommend setting this to a long, random value
in RT_SiteConfig.pm so that application-level crypto is not coupled to
the database credential. Set it before any user enrolls in MFA: changing it
later (or changing $DatabasePassword while it is empty) makes stored TOTP
secrets undecryptable, so all enrolled users have to reset MFA and re-enroll.