16 NEVER EDIT RT_Config.pm.
18 Instead, copy any sections you want to change to F<RT_SiteConfig.pm> and edit them there.
22 =head1 Base Configuration
28 C<$rtname> is the string that RT will look for in mail messages to
29 figure out what ticket a new piece of mail belongs to.
31 Your domain name is recommended, so as not to pollute the namespace.
32 once you start using a given tag, you should probably never change it.
33 (otherwise, mail for existing tickets won't get put in the right place)
37 Set($rtname , "example.com");
40 =item C<$EmailSubjectTagRegex>
42 This regexp controls what subject tags RT recognizes as its own.
43 If you're not dealing with historical C<$rtname> values, you'll likely
44 never have to enable this feature.
46 Be VERY CAREFUL with it. Note that it overrides C<$rtname> for subject
47 token matching and that you should use only "non-capturing" parenthesis
48 grouping. For example:
50 C<Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i );>
54 C<Set($EmailSubjectTagRegex, qr/(example.com|example.org)/i );>
56 This setting would make RT behave exactly as it does without the
61 #Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i );
65 =item C<$Organization>
67 You should set this to your organization's DNS domain. For example,
68 I<fsck.com> or I<asylum.arkham.ma.us>. It's used by the linking interface to
69 guarantee that ticket URIs are unique and easy to construct.
73 Set($Organization , "example.com");
75 =item C<$MinimumPasswordLength>
77 C<$MinimumPasswordLength> defines the minimum length for user
78 passwords. Setting it to 0 disables this check.
82 Set($MinimumPasswordLength , "5");
86 C<$Timezone> is used to convert times entered by users into GMT and back again
87 It should be set to a timezone recognized by your local unix box.
91 Set($Timezone , 'US/Eastern');
95 =head1 Database Configuration
99 =item C<$DatabaseType>
101 Database driver being used; case matters.
103 Valid types are "mysql", "Oracle" and "Pg"
107 Set($DatabaseType , '@DB_TYPE@');
109 =item C<$DatabaseHost>, C<$DatabaseRTHost>
111 The domain name of your database server.
113 If you're running mysql and it's on localhost,
114 leave it blank for enhanced performance
118 Set($DatabaseHost , '@DB_HOST@');
119 Set($DatabaseRTHost , '@DB_RT_HOST@');
121 =item C<$DatabasePort>
123 The port that your database server is running on. Ignored unless it's
124 a positive integer. It's usually safe to leave this blank
128 Set($DatabasePort , '@DB_PORT@');
130 =item C<$DatabaseUser>
132 The name of the database user (inside the database)
136 Set($DatabaseUser , '@DB_RT_USER@');
138 =item C<$DatabasePassword>
140 Password the C<$DatabaseUser> should use to access the database
144 Set($DatabasePassword , '@DB_RT_PASS@');
146 =item C<$DatabaseName>
148 The name of the RT's database on your database server. For Oracle
149 it's SID, DB objects are created in L<$DatabaseUser>'s schema.
153 Set($DatabaseName , '@DB_DATABASE@');
155 =item C<$DatabaseRequireSSL>
157 If you're using Postgres and have compiled in SSL support,
158 set C<$DatabaseRequireSSL> to 1 to turn on SSL communication
162 Set($DatabaseRequireSSL , undef);
164 =item C<$UseSQLForACLChecks>
166 In RT for ages ACL are checked after search what in some situtations
167 result in empty search pages and wrong count of tickets.
169 Set C<$UseSQLForACLChecks> to 1 to use SQL and get rid of these problems.
171 However, this option is beta. In some cases it result in performance
172 improvements, but some setups can not handle it.
176 Set($UseSQLForACLChecks, undef);
178 =item C<$TicketsItemMapSize>
180 In RT at display page of a ticket and there is the current search,
181 then links for first, next, previous and last ticket are shown in
184 To build full map RT has to fetch full result set out of DB what can
185 eat lots of resourses. Using this option it's possible to limit number
188 Set C<$TicketsItemMapSize> to number of tickets you want RT to look
189 at to build the map. If full result set is bigger than that number
190 then there would be no 'last' link in the menu.
192 Set this to zero to return back to old behaviour.
196 Set($TicketsItemMapSize, 1000);
200 =head1 Incoming Mail Gateway Configuration
206 C<$OwnerEmail> is the address of a human who manages RT. RT will send
207 errors generated by the mail gateway to this address. This address
208 should _not_ be an address that's managed by your RT instance.
212 Set($OwnerEmail , 'root');
214 =item C<$LoopsToRTOwner>
216 If C<$LoopsToRTOwner> is defined, RT will send mail that it believes
217 might be a loop to C<$OwnerEmail>
221 Set($LoopsToRTOwner , 1);
225 If C<$StoreLoops> is defined, RT will record messages that it believes
226 to be part of mail loops.
228 As it does this, it will try to be careful not to send mail to the
229 sender of these messages
233 Set($StoreLoops , undef);
235 =item C<$MaxAttachmentSize>
237 C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored
240 For mysql and oracle, we set this size at 10 megabytes.
241 If you're running a postgres version earlier than 7.1, you will need
242 to drop this to 8192. (8k)
247 Set($MaxAttachmentSize , 10000000);
249 =item C<$TruncateLongAttachments>
251 C<$TruncateLongAttachments>: if this is set to a non-undef value,
252 RT will truncate attachments longer than C<$MaxAttachmentSize>.
256 Set($TruncateLongAttachments , undef);
258 =item C<$DropLongAttachments>
260 C<$DropLongAttachments>: if this is set to a non-undef value,
261 RT will silently drop attachments longer than C<MaxAttachmentSize>.
265 Set($DropLongAttachments , undef);
267 =item C<$ParseNewMessageForTicketCcs>
269 If C<$ParseNewMessageForTicketCcs> is true, RT will attempt to divine
270 Ticket 'Cc' watchers from the To and Cc lines of incoming messages
271 Be forewarned that if you have _any_ addresses which forward mail to
272 RT automatically and you enable this option without modifying
273 C<$RTAddressRegexp> below, you will get yourself into a heap of trouble.
277 Set($ParseNewMessageForTicketCcs , undef);
279 =item C<$RTAddressRegexp>
281 C<$RTAddressRegexp> is used to make sure RT doesn't add itself as a ticket CC if
282 the setting above is enabled. It is important that you set this to a
283 regular expression that matches all addresses used by your RT. This lets RT
284 avoid sending mail to itself. It will also hide RT addresses from the list of
285 "One-time Cc" and Bcc lists on ticket reply.
287 If you have a number of addresses configured in your RT database already, you
288 can generate a naive first pass regexp by using
290 perl etc/upgrade/generate-rtaddressregexp
294 Set($RTAddressRegexp , undef);
296 =item C<$CanonicalizeEmailAddressMatch>, C<$CanonicalizeEmailAddressReplace>
298 RT provides functionality which allows the system to rewrite
299 incoming email addresses. In its simplest form,
300 you can substitute the value in $<CanonicalizeEmailAddressReplace>
301 for the value in $<CanonicalizeEmailAddressMatch>
302 (These values are passed to the $<CanonicalizeEmailAddress> subroutine in
305 By default, that routine performs a C<s/$Match/$Replace/gi> on any address
310 #Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$');
311 #Set($CanonicalizeEmailAddressReplace , '@example.com');
313 =item C<$CanonicalizeEmailAddressMatch>
315 Set this to true and the create new user page will use the values that you
316 enter in the form but use the function CanonicalizeUserInfo in
321 Set($CanonicalizeOnCreate, 0);
323 =item C<$ValidateUserEmailAddresses>
325 If C<$ValidateUserEmailAddresses> is true, RT will refuse to create users with
326 an invalid email address (as specified in RFC 2822) or with an email address
327 made of multiple email adresses.
331 Set($ValidateUserEmailAddresses, undef);
333 =item C<@MailPlugins>
335 C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
336 to use; see L<rt-mailgate>
340 =item C<$UnsafeEmailCommands>
342 C<$UnsafeEmailCommands>, if set to true, enables 'take' and 'resolve'
343 as possible actions via the mail gateway. As its name implies, this
344 is very unsafe, as it allows email with a forged sender to possibly
345 resolve arbitrary tickets!
349 =item C<$ExtractSubjectTagMatch>, C<$ExtractSubjectTagNoMatch>
351 The default "extract remote tracking tags" scrip settings; these
352 detect when your RT is talking to another RT, and adjusts the
357 Set($ExtractSubjectTagMatch, qr/\[.+? #\d+\]/);
358 Set($ExtractSubjectTagNoMatch, ( ${RT::EmailSubjectTagRegex}
359 ? qr/\[(?:${RT::EmailSubjectTagRegex}) #\d+\]/
360 : qr/\[\Q$RT::rtname\E #\d+\]/));
364 =head1 Outgoing Mail Configuration
368 =item C<$MailCommand>
370 C<$MailCommand> defines which method RT will use to try to send mail.
371 We know that 'sendmailpipe' works fairly well. If 'sendmailpipe'
372 doesn't work well for you, try 'sendmail'. Other options are 'smtp'
375 Note that you should remove the '-t' from C<$SendmailArguments>
376 if you use 'sendmail' rather than 'sendmailpipe'
378 For testing purposes, or to simply disable sending mail out into the world, you
379 can set C<$MailCommand> to 'testfile' which writes all mail to a temporary
380 file. RT will log the location of the temporary file so you can extract mail
385 Set($MailCommand , 'sendmailpipe');
387 =item C<$SetOutgoingMailFrom>
389 C<$SetOutgoingMailFrom> tells RT to set the sender envelope with the correspond
390 mail address of the ticket's queue.
392 Warning: If you use this setting, bounced mails will appear to be incoming
393 mail to the system, thus creating new tickets.
397 Set($SetOutgoingMailFrom, 0);
399 =item C<$OverrideOutgoingMailFrom>
401 C<$OverrideOutgoingMailFrom> is used for overwriting the Correspond
402 address of the queue as it is handed to sendmail -f. This helps force
403 the From_ header away from www-data or other email addresses that show
404 up in the "Sent by" line in Outlook.
406 The option is a hash reference of queue name to email address.
408 If there is no ticket involved, then the value of the C<Default> key will be
413 Set($OverrideOutgoingMailFrom, {
414 # 'Default' => 'admin@rt.example.com',
415 # 'General' => 'general@rt.example.com',
420 =item C<$DefaultMailPrecedence>
422 C<$DefaultMailPrecedence> is used to control the default
423 Precedence level of outgoing mail where none is specified.
424 By default it is C<bulk>, but if you only send mail to
425 your staff, you may wish to change it.
427 Note that you can set the precedence of individual templates
428 by including an explicit Precedence header.
430 If you set this value to C<undef> then we do not set a default
431 Precedence header to outgoing mail. However, if there already is a
432 Precedence header it will be preserved.
436 Set($DefaultMailPrecedence, 'bulk');
440 =item C<$DefaultErrorMailPrecedence>
442 C<$DefaultErrorMailPrecedence> is used to control the default
443 Precedence level of outgoing mail that indicates some kind of
444 error condition. By default it is C<bulk>, but if you only send
445 mail to your staff, you may wish to change it.
447 If you set this value to C<undef> then we do not add a Precedence
448 header to error mail.
452 Set($DefaultErrorMailPrecedence, 'bulk');
456 =item C<$UseOriginatorHeader>
458 C<$UseOriginatorHeader> is used to control the insertion of an
459 RT-Originator Header in every outgoing mail, containing the
460 mail address of the transaction creator.
464 Set($UseOriginatorHeader, 1);
468 =head1 Sendmail Configuration
470 These options only take effect if C<$MailCommand> is 'sendmail' or
475 =item C<$SendmailArguments>
477 C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
478 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
479 These options are good for most sendmail wrappers and workalikes
481 These arguments are good for sendmail brand sendmail 8 and newer
482 C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
486 Set($SendmailArguments , "-oi -t");
489 =item C<$SendmailBounceArguments>
491 C<$SendmailBounceArguments> defines what flags to pass to C<$Sendmail>
492 assuming RT needs to send an error (ie. bounce).
496 Set($SendmailBounceArguments , '-f "<>"');
498 =item C<$SendmailPath>
500 If you selected 'sendmailpipe' above, you MUST specify the path to
501 your sendmail binary in C<$SendmailPath>.
505 Set($SendmailPath , "/usr/sbin/sendmail");
510 =head1 SMTP Configuration
512 These options only take effect if C<$MailCommand> is 'smtp'
518 C<$SMTPServer> should be set to the hostname of the SMTP server to use
522 Set($SMTPServer, undef);
526 C<$SMTPFrom> should be set to the 'From' address to use, if not the
531 Set($SMTPFrom, undef);
535 C<$SMTPDebug> should be set to true to debug SMTP mail sending
543 =head1 Other Mailer Configuration
549 C<@MailParams> defines a list of options passed to $MailCommand if it
550 is not 'sendmailpipe', 'sendmail', or 'smtp'
554 Set(@MailParams, ());
556 =item C<$CorrespondAddress>, C<$CommentAddress>
558 RT is designed such that any mail which already has a ticket-id associated
559 with it will get to the right place automatically.
561 C<$CorrespondAddress> and C<$CommentAddress> are the default addresses
562 that will be listed in From: and Reply-To: headers of correspondence
563 and comment mail tracked by RT, unless overridden by a queue-specific
568 Set($CorrespondAddress , '');
570 Set($CommentAddress , '');
572 =item C<$DashboardAddress>
574 The email address from which RT will send dashboards. If none is set, then
575 C<$OwnerEmail> will be used.
579 Set($DashboardAddress, '');
581 =item C<$UseFriendlyFromLine>
583 By default, RT sets the outgoing mail's "From:" header to
584 "SenderName via RT". Setting C<$UseFriendlyFromLine> to 0 disables it.
588 Set($UseFriendlyFromLine, 1);
590 =item C<$FriendlyFromLineFormat>
592 C<sprintf()> format of the friendly 'From:' header; its arguments
593 are SenderName and SenderEmailAddress.
597 Set($FriendlyFromLineFormat, "\"%s via RT\" <%s>");
599 =item C<$UseFriendlyToLine>
601 RT can optionally set a "Friendly" 'To:' header when sending messages to
602 Ccs or AdminCcs (rather than having a blank 'To:' header.
604 This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL
605 If you are using sendmail, rather than postfix, qmail, exim or some other MTA,
606 you _must_ disable this option.
610 Set($UseFriendlyToLine, 0);
612 =item C<$FriendlyToLineFormat>
614 C<sprintf()> format of the friendly 'To:' header; its arguments
615 are WatcherType and TicketId.
619 Set($FriendlyToLineFormat, "\"%s of ". RT->Config->Get('rtname') ." Ticket #%s\":;");
621 =item C<$NotifyActor>
623 By default, RT doesn't notify the person who performs an update, as they
624 already know what they've done. If you'd like to change this behaviour,
625 Set C<$NotifyActor> to 1
629 Set($NotifyActor, 0);
631 =item C<$RecordOutgoingEmail>
633 By default, RT records each message it sends out to its own internal database.
634 To change this behavior, set C<$RecordOutgoingEmail> to 0
638 Set($RecordOutgoingEmail, 1);
640 =item C<$VERPPrefix>, C<$VERPPrefix>
642 VERP support (http://cr.yp.to/proto/verp.txt)
644 uncomment the following two directives to generate envelope senders
645 of the form C<${VERPPrefix}${originaladdress}@${VERPDomain}>
646 (i.e. rt-jesse=fsck.com@rt.example.com ).
648 This currently only works with sendmail and sendmailppie.
652 # Set($VERPPrefix, 'rt-');
653 # Set($VERPDomain, $RT::Organization);
656 =item C<$ForwardFromUser>
658 By default, RT forwards a message using queue's address and adds RT's tag into
659 subject of the outgoing message, so recipients' replies go into RT as correspondents.
661 To change this behavior, set C<$ForwardFromUser> to true value and RT will use
662 address of the current user and leave subject without RT's tag.
666 Set($ForwardFromUser, 0);
668 =item C<$ShowBccHeader>
670 By default RT hides from the web UI information about blind copies user sent on
673 To change this set the following option to true value.
677 Set($ShowBccHeader, 0);
679 =item C<$DashboardSubject>
681 Lets you set the subject of dashboards. Arguments are the frequency (Daily,
682 Weekly, Monthly) of the dashboard and the dashboard's name. [_1] for the name
687 Set($DashboardSubject, '%s Dashboard: %s');
691 =head1 GnuPG Configuration
693 A full description of the (somewhat extensive) GnuPG integration can be found
694 by running the command `perldoc L<RT::Crypt::GnuPG>` (or `perldoc
695 lib/RT/Crypt/GnuPG.pm` from your RT install directory).
701 Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and
702 signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
704 If you want to allow people to encrypt attachments inside the DB then
705 set C<AllowEncryptDataInDB> to true
707 Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
708 emails encrypted for key RT doesn't have and can not decrypt.
710 Set C<RejectOnBadData> to false if you don't want to reject letters
711 with incorrect GnuPG data.
717 OutgoingMessagesFormat => 'RFC', # Inline
718 AllowEncryptDataInDB => 0,
720 RejectOnMissingPrivateKey => 1,
721 RejectOnBadData => 1,
724 =item C<%GnuPGOptions>
726 Options of GnuPG program.
728 If you override this in your RT_SiteConfig, you should be sure
729 to include a homedir setting.
731 NOTE that options with '-' character MUST be quoted.
736 homedir => '@RT_VAR_PATH@/data/gpg',
739 # keyserver => 'hkp://subkeys.pgp.net',
741 # enables the automatic retrieving of keys when encrypting
742 # 'auto-key-locate' => 'keyserver',
744 # enables the automatic retrieving of keys when verifying signatures
745 # 'auto-key-retrieve' => undef,
751 =head1 Logging Configuration
753 The default is to log anything except debugging
754 information to syslog. Check the L<Log::Dispatch> POD for
755 information about how to get things by syslog, mail or anything
756 else, get debugging info in the log, etc.
758 It might generally make sense to send error and higher by email to
759 some administrator. If you do this, be careful that this email
760 isn't sent to this RT instance. Mail loops will generate a critical
765 =item C<$LogToSyslog>, C<$LogToScreen>
767 The minimum level error that will be logged to the specific device.
768 From lowest to highest priority, the levels are:
769 debug info notice warning error critical alert emergency
773 Set($LogToSyslog , 'info');
774 Set($LogToScreen , 'info');
776 =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
778 Logging to a standalone file is also possible, but note that the
779 file should needs to both exist and be writable by all direct users
780 of the RT API. This generally include the web server, whoever
781 rt-crontool runs as. Note that as rt-mailgate and the RT CLI go
782 through the webserver, so their users do not need to have write
783 permissions to this file. If you expect to have multiple users of
784 the direct API, Best Practical recommends using syslog instead of
789 Set($LogToFile , undef);
790 Set($LogDir, '@RT_LOG_PATH@');
791 Set($LogToFileNamed , "rt.log"); #log to rt.log
793 =item C<$LogStackTraces>
795 If set to a log level then logging will include stack traces for
796 messages with level equal to or greater than specified.
798 NOTICE: Stack traces include parameters supplied to functions or
799 methods. It is possible for stack trace logging to reveal sensitive
800 information such as passwords or ticket content in your logs.
804 Set($LogStackTraces, '');
806 =item C<@LogToSyslogConf>
808 On Solaris or UnixWare, set to ( socket => 'inet' ). Options here
809 override any other options RT passes to L<Log::Dispatch::Syslog>.
810 Other interesting flags include facility and logopt. (See the
811 L<Log::Dispatch::Syslog> documentation for more information.) (Maybe
812 ident too, if you have multiple RT installations.)
816 Set(@LogToSyslogConf, ());
818 =item C<$StatementLog>,
820 RT has rudimentary SQL statement logging support if you have
821 DBIx-SearchBuilder 1.31_1 or higher; simply set C<$StatementLog> to be
822 the level that you wish SQL statements to be logged at.
826 Set($StatementLog, undef);
830 =head1 Web Interface Configuration
834 =item C<$WebDefaultStylesheet>
836 This determines the default stylesheet the RT web interface will use.
837 RT ships with several themes by default:
839 web2 The totally new, default layout for RT 3.8
840 3.5-default RT 3.5 and 3.6 original layout
841 3.4-compat A 3.4 compatibility stylesheet to make RT look
844 This bundled distibution of RT also includes (enabled by default):
845 freeside2.1 Integration with Freeside
847 This value actually specifies a directory in F<share/html/NoAuth/css/>
848 from which RT will try to load the file main.css (which should
849 @import any other files the stylesheet needs). This allows you to
850 easily and cleanly create your own stylesheets to apply to RT. This
851 option can be overridden by users in their preferences.
855 Set($WebDefaultStylesheet, 'freeside2.1');
857 =item C<$UsernameFormat>
859 This determines how user info is displayed. 'concise' will show one of
860 either NickName, RealName, Name or EmailAddress, depending on what exists
861 and whether the user is privileged or not. 'verbose' will show RealName and
866 Set($UsernameFormat, 'verbose');
870 Domain name of the RT server, eg 'www.example.com'. It should not contain
871 anything else, but server name.
875 Set( $WebDomain, 'localhost' );
879 If we're running as a superuser, run on port 80
880 Otherwise, pick a high port for this user.
882 443 is default port for https protocol.
886 Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
890 If you're putting the web ui somewhere other than at the root of
891 your server, you should set C<$WebPath> to the path you'll be
894 C<$WebPath> requires a leading / but no trailing /, or it can be blank.
896 In most cases, you should leave C<$WebPath> set to '' (an empty value).
902 =item C<$WebBaseURL>, C<$WebURL>
904 Usually you don't want to set these options. The only obviouse reason is
905 RT accessible via https protocol on non standard port, eg
906 'https://rt.example.com:9999'. In all other cases these options are computed
907 using C<$WebDomain>, C<$WebPort> and C<$WebPath>.
909 C<$WebBaseURL> is the scheme, server and port (eg 'http://rt.example.com')
910 for constructing urls to the web UI. C<$WebBaseURL> doesn't need a trailing /.
912 C<$WebURL> is the C<$WebBaseURL>, C<$WebPath> and trailing /, for example:
913 'http://www.example.com/rt/'.
917 my $port = RT->Config->Get('WebPort');
919 ($port == 443? 'https': 'http') .'://'
920 . RT->Config->Get('WebDomain')
921 . ($port != 80 && $port != 443? ":$port" : '')
924 Set($WebURL, RT->Config->Get('WebBaseURL') . RT->Config->Get('WebPath') . "/");
926 =item C<$WebImagesURL>
928 C<$WebImagesURL> points to the base URL where RT can find its images.
929 Define the directory name to be used for images in rt web
934 Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/");
938 C<$LogoURL> points to the URL of the RT logo displayed in the web UI
942 Set($LogoURL, RT->Config->Get('WebImagesURL') . "bplogo.gif");
944 =item C<$LogoLinkURL>
946 C<$LogoLinkURL> is the URL that the RT logo hyperlinks to.
950 Set($LogoLinkURL, "http://bestpractical.com");
952 =item C<$LogoAltText>
954 C<$LogoAltText> is a string of text for the alt-text of the logo. It
955 will be passed through C<loc> for localization.
959 Set($LogoAltText, "Best Practical Solutions, LLC corporate logo");
961 =item C<$LogoImageHeight>
963 C<$LogoImageHeight> is the value of the C<height> attribute of the logo
968 Set($LogoImageHeight, 33);
970 =item C<$LogoImageWidth>
972 C<$LogoImageWidth> is the value of the C<width> attribute of the logo
977 Set($LogoImageWidth, 177);
979 =item C<$WebNoAuthRegex>
981 What portion of RT's URL space should not require authentication.
983 This is mostly for extension and doesn't mean RT will work without
984 login if you change it.
988 Set($WebNoAuthRegex, qr{^ /rt (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x );
990 =item C<$SelfServiceRegex>
992 What portion of RT's URLspace should be accessible to Unprivileged users
993 This does not override the redirect from F</Ticket/Display.html> to
994 F</SelfService/Display.html> when Unprivileged users attempt to access
999 Set($SelfServiceRegex, qr!^(?:/+SelfService/)!x );
1001 =item C<$MessageBoxWidth>, C<$MessageBoxHeight>
1003 For message boxes, set the entry box width, height and what type of
1004 wrapping to use. These options can be overridden by users in their
1007 Default width: 72, height: 15
1009 These settings only apply to the non-RichText message box.
1010 See below for Rich Text settings.
1014 Set($MessageBoxWidth, 72);
1015 Set($MessageBoxHeight, 15);
1017 =item C<$MessageBoxWrap>
1019 Default wrapping: "HARD" (choices "SOFT", "HARD")
1021 Wrapping is disabled when using MessageBoxRichText because
1022 of a bad interaction between IE and wrapping with the Rich
1027 Set($MessageBoxWrap, "HARD");
1029 =item C<$MessageBoxRichText>
1031 Should "rich text" editing be enabled? This option lets your users send html email messages from the web interface.
1035 Set($MessageBoxRichText, 1);
1037 =item C<$MessageBoxRichTextHeight>
1039 Height of RichText javascript enabled editing boxes (in pixels)
1043 Set($MessageBoxRichTextHeight, 200);
1045 =item C<$MessageBoxIncludeSignature>
1047 Should your user's signatures (from their Preferences page) be included in Comments and Replies
1051 Set($MessageBoxIncludeSignature, 1);
1053 =item C<$MessageBoxIncludeSignatureOnComment>
1055 Should your user's signatures (from their Preferences page) be included in Comments. Setting this to false overrides C<$MessageBoxIncludeSignature>.
1059 Set($MessageBoxIncludeSignatureOnComment, 1);
1061 =item C<$WikiImplicitLinks>
1063 Support implicit links in WikiText custom fields? A true value
1064 causes InterCapped or ALLCAPS words in WikiText fields to
1065 automatically become links to searches for those words. If used on
1066 RTFM articles, it links to the RTFM article with that name.
1070 Set($WikiImplicitLinks, 0);
1072 =item C<$TrustHTMLAttachments>
1074 if C<TrustHTMLAttachments> is not defined, we will display them
1075 as text. This prevents malicious HTML and javascript from being
1076 sent in a request (although there is probably more to it than that)
1080 Set($TrustHTMLAttachments, undef);
1082 =item C<$AlwaysDownloadAttachments>
1084 Always download attachments, regardless of content type. If set,
1085 this overrides C<TrustHTMLAttachments>.
1089 Set($AlwaysDownloadAttachments, undef);
1091 =item C<$AttachmentUnits>
1093 Controls the units (kilobytes or bytes) that attachment sizes use
1094 for display. The default is to display kilobytes if the attachment
1095 is larger than 1024 bytes, bytes otherwise. If you set
1096 C<$AttachmentUnits> to C<'k'> then attachment sizes will always be
1097 displayed in kilobytes. If set to C<'b'>, then sizes will be bytes.
1101 Set($AttachmentUnits, undef);
1103 =item C<$EditCustomFieldsSingleColumn>
1105 When displaying a list of Ticket Custom Fields for editing, RT defaults
1106 to a 2 column list. If you set this to 1, it will instead display the
1107 Custom Fields in a single column.
1111 Set($EditCustomFieldsSingleColumn, 0);
1113 =item C<$RedistributeAutoGeneratedMessages>
1115 Should RT redistribute correspondence that it identifies as
1116 machine generated? A true value will do so; setting this to '0'
1117 will cause no such messages to be redistributed.
1118 You can also use 'privileged' (the default), which will redistribute
1119 only to privileged users. This helps to protect against malformed
1120 bounces and loops caused by autocreated requestors with bogus addresses.
1124 Set($RedistributeAutoGeneratedMessages, 'privileged');
1126 =item C<$PreferRichText>
1128 If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
1129 messages in preference to their plaintext alternatives. RT "scrubs" the
1130 html to show only a minimal subset of HTML to avoid possible contamination
1131 by cross-site-scripting attacks.
1135 Set($PreferRichText, undef);
1137 =item C<$WebExternalAuth>
1139 If C<$WebExternalAuth> is defined, RT will defer to the environment's
1140 REMOTE_USER variable.
1144 Set($WebExternalAuth, undef);
1146 =item C<$WebExternalAuthContinuous>
1148 If C<$WebExternalAuthContinuous> is defined, RT will check for the
1149 REMOTE_USER on each access. If you would prefer this to only happen
1150 once (at initial login) set this to a false value. The default setting
1151 will help ensure that if your external auth system deauthenticates a
1152 user, RT notices as soon as possible.
1156 Set($WebExternalAuthContinuous, 1);
1158 =item C<$WebFallbackToInternalAuth>
1160 If C<$WebFallbackToInternalAuth> is defined, the user is allowed a chance
1161 of fallback to the login screen, even if REMOTE_USER failed.
1165 Set($WebFallbackToInternalAuth , undef);
1167 =item C<$WebExternalGecos>
1169 C<$WebExternalGecos> means to match 'gecos' field as the user identity);
1170 useful with mod_auth_pwcheck and IIS Integrated Windows logon.
1174 Set($WebExternalGecos , undef);
1176 =item C<$WebExternalAuto>
1178 C<$WebExternalAuto> will create users under the same name as REMOTE_USER
1179 upon login, if it's missing in the Users table.
1183 Set($WebExternalAuto , undef);
1185 =item C<$AutoCreate>
1187 If C<$WebExternalAuto> is true, C<$AutoCreate> will be passed to User's
1188 Create method. Use it to set defaults, such as creating
1189 Unprivileged users with C<{ Privileged => 0 }>
1190 ( Must be a hashref of arguments )
1194 Set($AutoCreate, undef);
1196 =item C<$WebSessionClass>
1198 C<$WebSessionClass> is the class you wish to use for managing Sessions.
1199 It defaults to use your SQL database, but if you are using MySQL 3.x and
1200 plans to use non-ascii Queue names, uncomment and add this line to
1201 F<RT_SiteConfig.pm> will prevent session corruption.
1205 # Set($WebSessionClass , 'Apache::Session::File');
1207 =item C<$AutoLogoff>
1209 By default, RT's user sessions persist until a user closes his or her
1210 browser. With the C<$AutoLogoff> option you can setup session lifetime in
1211 minutes. A user will be logged out if he or she doesn't send any requests
1212 to RT for the defined time.
1216 Set($AutoLogoff, 0);
1218 =item C<$LogoutRefresh>
1220 The number of seconds to wait after logout before sending the user to the
1221 login page. By default, 1 second, though you may want to increase this if
1222 you display additional information on the logout page.
1226 Set($LogoutRefresh, 1);
1228 =item C<$WebSecureCookies>
1230 By default, RT's session cookie isn't marked as "secure" Some web browsers
1231 will treat secure cookies more carefully than non-secure ones, being careful
1232 not to write them to disk, only send them over an SSL secured connection
1233 and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value.
1234 NOTE: You probably don't want to turn this on _unless_ users are only connecting
1235 via SSL encrypted HTTP connections.
1239 Set($WebSecureCookies, 0);
1241 =item C<$WebFlushDbCacheEveryRequest>
1243 By default, RT clears its database cache after every page view.
1244 This ensures that you've always got the most current information
1245 when working in a multi-process (mod_perl or FastCGI) Environment
1246 Setting C<$WebFlushDbCacheEveryRequest> to '0' will turn this off,
1247 which will speed RT up a bit, at the expense of a tiny bit of data
1252 Set($WebFlushDbCacheEveryRequest, '1');
1255 =item C<$MaxInlineBody>
1257 C<$MaxInlineBody> is the maximum attachment size that we want to see
1258 inline when viewing a transaction. RT will inline any text if value
1259 is undefined or 0. This option can be overridden by users in their
1264 Set($MaxInlineBody, 12000);
1266 =item C<$DefaultSummaryRows>
1268 C<$DefaultSummaryRows> is default number of rows displayed in for search
1269 results on the frontpage.
1273 Set($DefaultSummaryRows, 10);
1275 =item C<$HomePageRefreshInterval>
1277 C<$HomePageRefreshInterval> is default number of seconds to refresh the RT
1278 home page. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1282 Set($HomePageRefreshInterval, 0);
1284 =item C<$SearchResultsRefreshInterval>
1286 C<$SearchResultsRefreshInterval> is default number of seconds to refresh
1287 search results in RT. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1291 Set($SearchResultsRefreshInterval, 0);
1293 =item C<$ResolveDefaultUpdateType>
1295 Set the default Update Type when clicking the Resolve link in the Ticket
1298 Comment Comments (Not sent to requestors)
1299 Respond Reply to requestors
1303 Set($ResolveDefaultUpdateType, 'Comment');
1305 =item C<$SuppressAutoOpenOnUpdate>
1307 When users click Comment or Reply on a new ticket in the web UI, the default
1308 status for the ticket gets set to 'open' if the status is currently 'new'.
1309 Setting this option to 1 will suppress that behavior and leave the default
1310 status as 'new'. This option can be overridden by users in their preferences.
1314 Set($SuppressAutoOpenOnUpdate, 0);
1316 =item C<$OldestTransactionsFirst>
1318 By default, RT shows newest transactions at the bottom of the ticket
1319 history page, if you want see them at the top set this to '0'. This
1320 option can be overridden by users in their preferences.
1324 Set($OldestTransactionsFirst, '1');
1326 =item C<$ShowTransactionImages>
1328 By default, RT shows images attached to incoming (and outgoing) ticket updates
1329 inline. Set this variable to 0 if you'd like to disable that behaviour
1333 Set($ShowTransactionImages, 1);
1335 =item C<$PlainTextPre>
1337 Normally plaintext attachments are displayed as HTML with line
1338 breaks preserved. This causes space- and tab-based formatting not
1339 to be displayed correctly. By setting $PlainTextPre they'll be
1340 displayed using <pre> instead so such formatting works, but they'll
1341 use a monospaced font, no matter what the value of C<$PlainTextMono> is.
1345 Set($PlainTextPre, 0);
1348 =item C<$PlainTextMono>
1349 To display plaintext attachments,
1350 Set C<$PlainTextMono> to 1 to use monospaced font and preserve
1351 formatting, but unlike PlainTextPre, the text will wrap to fit into the
1356 Set($PlainTextMono, 0);
1358 =item C<$ShowUnreadMessageNotifications>
1360 By default, RT will prompt users when there are new, unread messages on
1361 tickets they are viewing.
1363 Set C<$ShowUnreadMessageNotifications> to a false value to disable this feature.
1367 Set($ShowUnreadMessageNotifications, 1);
1370 =item C<$HomepageComponents>
1372 C<$HomepageComponents> is an arrayref of allowed components on a user's
1373 customized homepage ("RT at a glance").
1377 Set($HomepageComponents, [qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards)]);
1379 =item C<@MasonParameters>
1381 C<@MasonParameters> is the list of parameters for the constructor of
1382 HTML::Mason's Apache or CGI Handler. This is normally only useful
1383 for debugging, eg. profiling individual components with:
1385 use MasonX::Profiler; # available on CPAN
1386 Set(@MasonParameters, (preamble => 'my $p = MasonX::Profiler->new($m, $r);'));
1390 Set(@MasonParameters, ());
1392 =item C<$DefaultSearchResultFormat>
1394 C<$DefaultSearchResultFormat> is the default format for RT search results
1398 Set ($DefaultSearchResultFormat, qq{
1399 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1400 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1408 '<small>__Requestors__</small>',
1409 '<small>__CustomerTags__</small>',
1410 '<small>__CreatedRelative__</small>',
1411 '<small>__ToldRelative__</small>',
1412 '<small>__LastUpdatedRelative__</small>',
1413 '<small>__TimeLeft__</small>'});
1415 =item C<$DefaultSelfServiceSearchResultFormat>
1417 C<$DefaultSelfServiceSearchResultFormat> is the default format of searches displayed in the
1418 SelfService interface.
1422 Set($DefaultSelfServiceSearchResultFormat, qq{
1423 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1424 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1429 =item C<%AdminSearchResultFormat>
1431 In admin interface format strings similar to tickets search result
1432 formats are used. Use C<%AdminSearchResultFormat> to define format
1433 strings per RT class.
1437 Set(%AdminSearchResultFormat,
1439 q{'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1440 .q{,'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1441 .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__},
1444 q{'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1445 .q{,'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1446 .q{,'__Description__'},
1449 q{'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1450 .q{,'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1451 .q{,__RealName__, __EmailAddress__},
1454 q{'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1455 .q{,'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1456 .q{,__AppliedTo__, __FriendlyType__, __FriendlyPattern__},
1459 q{'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__id__</a>/TITLE:#'}
1460 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__Description__</a>/TITLE:Description'}
1461 .q{,__Stage__, __Condition__, __Action__, __Template__},
1464 q{'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__id__</a>/TITLE:#'}
1465 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__Name__</a>/TITLE:Name'}
1466 .q{,'__Description__'},
1469 =item C<$SuppressInlineTextFiles>
1471 If C<$SuppressInlineTextFiles> is set to a true value, then uploaded
1472 text files (text-type attachments with file names) are prevented
1473 from being displayed in-line when viewing a ticket's history.
1477 Set($SuppressInlineTextFiles, undef);
1479 =item C<$DontSearchFileAttachments>
1481 If C<$DontSearchFileAttachments> is set to a true value, then uploaded
1482 files (attachments with file names) are not searched during full-content
1487 Set($DontSearchFileAttachments, undef);
1491 The L<GD> module (which RT uses for graphs) ships with a builtin font
1492 that doesn't have full Unicode support. You can use a given TrueType font
1493 for a specific language by setting %ChartFont to (language =E<gt> the
1494 absolute path of a font) pairs. Your GD library must have support for
1495 TrueType fonts to use this option. If there is no entry for a language
1496 in the hash then font with 'others' key is used.
1498 RT comes with two TrueType fonts covering most available languages.
1504 'zh-cn' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1505 'zh-tw' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1506 'ja' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1507 'others' => "$RT::BasePath/share/fonts/DroidSans.ttf",
1510 =item C<$ChartsTimezonesInDB>
1512 RT stores dates using the UTC timezone in the DB, so charts grouped
1513 by dates and time are not representative. Set C<$ChartsTimezonesInDB>
1514 to a true value to enable timezone conversions using your DB's
1515 capabilities. You may need to do some work on the DB side to use this
1516 feature, read more in F<docs/timezones_in_charts.pod>.
1518 At this time, this feature only applies to MySQL and PostgreSQL.
1522 Set( $ChartsTimezonesInDB, 0 );
1524 =item C<@Active_MakeClicky>
1526 MakeClicky detects various formats of data in headers and email
1527 messages, and extends them with supporting links. By default, RT
1528 provides two formats:
1530 * 'httpurl': detects http:// and https:// URLs and adds '[Open URL]'
1533 * 'httpurl_overwrite': also detects URLs as 'httpurl' format, but
1534 replace URL with link and *adds spaces* into text if it's longer
1535 then 30 chars. This allow browser to wrap long URLs and avoid
1536 horizontal scrolling.
1538 See F<share/html/Elements/MakeClicky> for documentation on how to add your own.
1542 Set(@Active_MakeClicky, qw());
1544 =item C<$DefaultQueue>
1546 Use this to select the default queue name that will be used for creating new
1547 tickets. You may use either the queue's name or its ID. This only affects the
1548 queue selection boxes on the web interface.
1552 #Set($DefaultQueue, 'General');
1554 =item C<$DefaultTimeUnitsToHours>
1556 Use this to set the default units for time entry to hours instead of minutes.
1560 Set($DefaultTimeUnitsToHours, 0);
1562 =item C<$SimpleSearchIncludeResolved>
1564 By default, the simple ticket search in the top bar excludes "resolved" tickets
1565 unless a status argument is specified. Set this to a true value to include
1570 Set($SimpleSearchIncludeResolved, 0);
1574 =head1 L<Net::Server> (rt-server) Configuration
1578 =item C<$StandaloneMinServers>, C<$StandaloneMaxServers>
1580 The absolute minimum and maximum number of servers that will be created to
1581 handle requests. Having multiple servers means that serving a slow page will
1582 affect other users less.
1586 Set($StandaloneMinServers, 1);
1587 Set($StandaloneMaxServers, 1);
1589 =item C<$StandaloneMinSpareServers>, C<$StandaloneMaxSpareServers>
1591 These next two options can be used to scale up and down the number of servers
1592 to adjust to load. These two options will respect the C<$StandaloneMinServers
1593 > and C<$StandaloneMaxServers options>.
1597 Set($StandaloneMinSpareServers, 0);
1598 Set($StandaloneMaxSpareServers, 0);
1600 =item C<$StandaloneMaxRequests>
1602 This sets the absolute maximum number of requests a single server will serve.
1603 Setting this would be useful if, for example, memory usage slowly crawls up
1608 #Set($StandaloneMaxRequests, 50);
1610 =item C<%NetServerOptions>
1612 C<%NetServerOptions> is a hash of additional options to use for
1613 L<Net::Server/DEFAULT ARGUMENTS>. For example, you could set
1614 reverse_lookups to get the hostnames for all users with:
1616 C<Set(%NetServerOptions, (reverse_lookups => 1));>
1620 Set(%NetServerOptions, ());
1625 =head1 UTF-8 Configuration
1629 =item C<@LexiconLanguages>
1631 An array that contains languages supported by RT's internationalization
1632 interface. Defaults to all *.po lexicons; setting it to C<qw(en ja)> will make
1633 RT bilingual instead of multilingual, but will save some memory.
1637 Set(@LexiconLanguages, qw(*));
1639 =item C<@EmailInputEncodings>
1641 An array that contains default encodings used to guess which charset
1642 an attachment uses if not specified. Must be recognized by
1647 Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
1649 =item C<$EmailOutputEncoding>
1651 The charset for localized email. Must be recognized by Encode.
1655 Set($EmailOutputEncoding, 'utf-8');
1660 =head1 Date Handling Configuration
1664 =item C<$DateTimeFormat>
1666 You can choose date and time format. See "Output formatters"
1667 section in perldoc F<lib/RT/Date.pm> for more options. This option can
1668 be overridden by users in their preferences.
1671 C<Set($DateTimeFormat, 'LocalizedDateTime');>
1672 C<Set($DateTimeFormat, { Format => 'ISO', Seconds => 0 });>
1673 C<Set($DateTimeFormat, 'RFC2822');>
1674 C<Set($DateTimeFormat, { Format => 'RFC2822', Seconds => 0, DayOfWeek => 0 });>
1678 Set($DateTimeFormat, 'DefaultFormat');
1680 # Next two options are for Time::ParseDate
1682 =item C<$DateDayBeforeMonth>
1684 Set this to 1 if your local date convention looks like "dd/mm/yy" instead of
1685 "mm/dd/yy". Used only for parsing, not for displaying dates.
1689 Set($DateDayBeforeMonth , 1);
1691 =item C<$AmbiguousDayInPast>, C<$AmbiguousDayInFuture>
1693 Should an unspecified day or year in a date refer to a future or a
1694 past value? For example, should a date of "Tuesday" default to mean
1695 the date for next Tuesday or last Tuesday? Should the date "March 1"
1696 default to the date for next March or last March?
1698 Set $<AmbiguousDayInPast> for the last date, or $<$AmbiguousDayInFuture> for the
1701 The default is usually good.
1705 Set($AmbiguousDayInPast, 0);
1706 Set($AmbiguousDayInFuture, 0);
1710 =head1 Approval Configuration
1712 Configuration for the approval system
1716 =item C<$ApprovalRejectionNotes>
1718 Should rejection notes be sent to the requestors? The default is true.
1722 Set($ApprovalRejectionNotes, 1);
1727 =head1 Miscellaneous Configuration
1731 =item C<@ActiveStatus>, C<@InactiveStatus>
1733 You can define new statuses and even reorder existing statuses here.
1734 WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
1735 will break horribly. The statuses you add must be no longer than
1740 Set(@ActiveStatus, qw(new open stalled));
1741 Set(@InactiveStatus, qw(resolved rejected deleted));
1743 =item C<$LinkTransactionsRun1Scrip>
1745 RT-3.4 backward compatibility setting. Add/Delete Link used to record one
1746 transaction and run one scrip. Set this value to 1 if you want
1747 only one of the link transactions to have scrips run.
1751 Set($LinkTransactionsRun1Scrip, 0);
1753 =item C<$StrictLinkACL>
1755 When this feature is enabled a user needs I<ModifyTicket> rights on both
1756 tickets to link them together, otherwise he can have rights on either of
1761 Set($StrictLinkACL, 1);
1763 =item C<$PreviewScripMessages>
1765 Set C<$PreviewScripMessages> to 1 if the scrips preview on the ticket
1766 reply page should include the content of the messages to be sent.
1770 Set($PreviewScripMessages, 0);
1772 =item C<$UseTransactionBatch>
1774 Set C<$UseTransactionBatch> to 1 to execute transactions in batches,
1775 such that a resolve and comment (for example) would happen
1776 simultaneously, instead of as two transactions, unaware of each
1781 Set($UseTransactionBatch, 1);
1783 =item C<@CustomFieldValuesSources>
1785 Set C<@CustomFieldValuesSources> to a list of class names which extend
1786 L<RT::CustomFieldValues::External>. This can be used to pull lists of
1787 custom field values from external sources at runtime.
1791 Set(@CustomFieldValuesSources, ());
1793 =item C<$CanonicalizeRedirectURLs>
1795 Set C<$CanonicalizeRedirectURLs> to 1 to use $C<WebURL> when redirecting rather
1796 than the one we get from C<%ENV>.
1798 If you use RT behind a reverse proxy, you almost certainly want to
1803 Set($CanonicalizeRedirectURLs, 0);
1804 =item C<$EnableReminders>
1806 Hide links/portlets related to Reminders by setting this to 0
1810 Set($EnableReminders,1);
1815 Set C<@Plugins> to a list of external RT plugins that should be enabled (those
1816 plugins have to be previously downloaded and installed).
1819 C<Set(@Plugins, (qw(Extension::QuickDelete RT::FM)));>
1823 Set(@Plugins, (qw(RTx::Calendar))); #RTx::Checklist ));
1827 =head1 Development Configuration
1833 RT comes with a "Development mode" setting.
1834 This setting, as a convenience for developers, turns on
1835 all sorts of development options that you most likely don't want in
1838 * Turns off Mason's 'static_source' directive. By default, you can't
1839 edit RT's web ui components on the fly and have RT magically pick up
1840 your changes. (It's a big performance hit)
1846 Set($DevelMode, '@RT_DEVEL_MODE@');
1851 =head1 Deprecated Options
1855 =item C<$AlwaysUseBase64>
1857 Encode blobs as base64 in DB (?)
1859 =item C<$TicketBaseURI>
1861 Base URI to tickets in this system; used when loading (?)
1863 =item C<$UseCodeTickets>
1865 This option is exists for backwards compatibility. Don't use it.