Well as “no answer was the stern reply” I’ve had to dive in myself, and add a suitable option. In case it helps others, here’s what I did:
-
make a local copy of
/opt/rt5/lib/RT/Config.pm
in/opt/rt5/local/lib/RT/Config.pm
-
Apply this minor change to the local version:
2495c2495,2499 < foreach (qw(Package File Line SiteConfig Extension Database)) { --- > my @ConfigSources = qw(Package File Line SiteConfig Extension Database); > if($self->Get('ConfigFromFiles')) { > @ConfigSources = qw(Package File Line SiteConfig Extension); > } > foreach (@ConfigSources) {
-
Put the line
Set($ConfigFromFiles, 1);
on the end of my/opt/rt5/local/etc/RT_SiteConfig.pm
-
Flush Mason cache and restart web server.
Now the lifecycles we see in RT are the ones from the site config files, not from the database. Hoorah!