On 22/02/2012 12:48, Jaime Kikpole wrote:

It's a FreeBSD ports thing -- ports generally do not provide pre-packaged configurations, on the basis that is what sysadmins are for.

No -- as I said, the port doesn't touch the database at all. What it does do is print out a message with some instructions on what to do next. Actually, these are pretty much a condensed version of what is in the README in the rt-4.0.5 sources.

To create a brand-new empty database and associated userid and password for rt-4.0.5 run:

/usr/local/sbin/rt-setup-database --action create,acl \ --prompt-for-dba-password

This will use the defaults specified when you built the port, prompting you for the password for the privileged DBA login used to do the schema modification bits. (While you can set that at build time, I don't recommend it on the basis that it will store the password internally in plain text.) You may need to do other dba related bits, like editing the pg_hba.conf file to allow the new user appropriate access levels.

For upgrades from rt-3.x to rt-4.x, the procedure would be to start with a copy of your rt3 DB loaded into a new rt4 DB instance -- ie. by using mysqldump and mysql client to load, or pg_dump and psql to load or the equivalent for whatever RDBMS you prefer. Then use rt-setup-database to apply the required schema updates.

Note: although the rt40 port defaults to using MySQL, personally, I'd choose PostgreSQL for a new install. (Pg supports full-text indexing natively, whereas MySQL needs external software and more to do so.) Switching RDBMSes as part of the upgrade is not a trivial operation, so unless you have good reason, just stick with whatever DB you've already got.

The DB default of MySQL is what was there historically, and I didn't think my arbitrarily changing that was justified.

rt40 can be run with any web server supported by PSGI, which is rather more than just Apache. (There's even a built-in pure-perl one, but that's really not suitable for any sort of serious usage level.) While apache22 is the default, p5-Log-Dispatch doesn't have any apache dependencies that I can see...

How hard the apache upgrade is for you depends on what else you serve with your apache13 instance currently. If this is a server dedicated to RT, then it should be pretty simple. For a dedicated RT VHOST (or a dedicated apache instance), and assuming a) you're using mod_perl and b) you want to use HTTPS, the rt-related config should look something like this:

<VirtualHost 192.0.2.40:443> ServerName rt.example.org

SSLEngine on SSLCertificateFile www/apache22/certs/rt.example.org-cert.pem SSLCertificateKeyFile www/apache22/certs/rt.example.org-key.pem

AddDefaultCharset UTF-8

DocumentRoot "/usr/local/share/rt40/html" <Location /> Order Allow,Deny Allow from 192.0.2.0/24

SetHandler modperl PerlResponseHandler Plack::Handler::Apache2 PerlSetVar psgi_app /usr/local/sbin/rt-server </Location> <Perl> use Plack::Handler::Apache2; Plack::Handler::Apache2->preload("/usr/local/sbin/rt-server"); </Perl> </VirtualHost>

(Just drop the lines starting SSL and change the port number to 80 if you prefer plain text HTTP.)

There are some more examples in the RT supplied documentation in /usr/local/share/doc/rt40/web_deployment.pod

I think there may well be moves to drop perl-5.8 support from ports in the relatively near future. If you're going to be having an update-fest anyhow, then I'd recommend switching to perl-5.12 instead.

Thank you.

Cheers,

Matthew