Valid types are "mysql", "Oracle", and "Pg". These paths will be checked before any plugin or core static paths.ĭatabase driver being used case matters. The contents of each hashref should be the the same arguments as Plack::Middleware::Static takes. to serve extra paths with a static handler. RT-Extension-JSGantt) instead of the package name ( RT::Extension::JSGantt). RT will also accept the distribution name (i.e. a plugin has been downloaded and installed, use Plugin() to add to the enabled list: Plugin( "RT::Extension::JSGantt" ) It should be set to a timezone recognized by your server. $Timezone is the default timezone, used to convert times entered by users into GMT, as they are stored in the database, and back again users can override this. In most cases, you should leave $WebPath set to "" (an empty value). $WebPath requires a leading / but no trailing /, or it can be blank. If you're putting the web UI somewhere other than at the root of your server, you should set $WebPath to the path you'll be serving RT at. Otherwise, pick a high port for this user.Ĥ43 is default port for https protocol. If we're running as a superuser, run on port 80. 'It should not contain anything except the server name. $WebDomainĭomain name of the RT server, e.g. They should be set to email addresses which have been configured as aliases for rt-mailgate. $CorrespondAddress and $CommentAddress are the default addresses that will be listed in From: and Reply-To: headers of correspondence and comment mail tracked by RT, unless overridden by a queue-specific address. RT is designed such that any mail which already has a ticket-id associated with it will get to the right place automatically. Changing it after you have created tickets in the system will break all existing ticket links! $CorrespondAddress, $CommentAddress It is used by the linking interface to guarantee that ticket URIs are unique and easy to construct. You should set this to your organization's DNS domain. Once you start using a given tag, you should probably never change it otherwise, mail for existing tickets won't get put in the right place. Your domain name is recommended, so as not to pollute the namespace. $rtname is the string that RT will look for in mail messages to figure out what ticket a new piece of mail belongs to. This prevents changes that could make your RT inoperable, leaving you unable to restore the system via the web UI. Some settings that are core to RT cannot be changed via the web interface. If you provide a custom setting in both places, RT will issue a warning in the log as a reminder to consider removing the setting from etc/RT_SiteConfig.pm to avoid confusion. Any configuration options set there take precedence over values set in etc/RT_SiteConfig.pm. RT also allows you to set configuration via the RT web interface at Admin > Tools > System Configuration. More information about this option is available in the RT::Config documentation. If you have many customizations to manage, you can break your configuration into multiple files and put them in a directory etc/RT_SiteConfig.d/. The correct place to set site-specific options is in etc/RT_SiteConfig.pm. If you do, your changes will be lost when you upgrade and RT installs the newest version of this file on your system. You should never edit this file directly. This file, etc/RT_Config.pm, defines the available configuration options and sets the defaults for RT. The available options and valid values are described below. RT has dozens of configuration options to customize how RT behaves for different situations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |