[Rt-commit] r14151 - in rt/branches/3.999-DANGEROUS: etc
sunnavy at bestpractical.com
sunnavy at bestpractical.com
Wed Jul 16 08:52:17 EDT 2008
Author: sunnavy
Date: Wed Jul 16 08:52:17 2008
New Revision: 14151
Modified:
rt/branches/3.999-DANGEROUS/ (props changed)
rt/branches/3.999-DANGEROUS/etc/RT_Config.pm
Log:
r14539 at sunnavys-mb: sunnavy | 2008-07-16 17:30:28 +0800
merged RT_Config.pm
Modified: rt/branches/3.999-DANGEROUS/etc/RT_Config.pm
==============================================================================
--- rt/branches/3.999-DANGEROUS/etc/RT_Config.pm (original)
+++ rt/branches/3.999-DANGEROUS/etc/RT_Config.pm Wed Jul 16 08:52:17 2008
@@ -1,11 +1,7 @@
-#
-# WARNING: NEVER EDIT RT_Config.pm. Instead, copy any sections you want to change to RT_SiteConfig.pm
-# and edit them there.
-#
package RT;
-=head1 name
+=head1 NAME
RT::Config
@@ -15,726 +11,1369 @@
=cut
-# {{{ base Configuration
+=head1 WARNING
-# $rtname is the string that RT will look for in mail messages to
-# figure out what ticket a new piece of mail belongs to
+NEVER EDIT RT_Config.pm.
-# Your domain name is recommended, so as not to pollute the namespace.
-# 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
+Instead, copy any sections you want to change to F<RT_SiteConfig.pm> and edit them there.
-set( $rtname, "example.com" );
+=cut
+
+=head1 Base Configuration
+
+=over 4
+
+=item C<$rtname>
+
+C<$rtname> is the string that RT will look for in mail messages to
+figure out what ticket a new piece of mail belongs to.
+
+Your domain name is recommended, so as not to pollute the namespace.
+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)
+
+=cut
+
+Set($rtname , "example.com");
+
+
+=item C<$EmailSubjectTagRegex>
+
+This regexp controls what subject tags RT recognizes as its own.
+If you're not dealing with historical C<$rtname> values, you'll likely
+never have to enable this feature.
+
+Be VERY CAREFUL with it. Note that it overrides C<$rtname> for subject
+token matching and that you should use only "non-capturing" parenthesis
+grouping. For example:
+
+C<Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i );>
+
+and NOT
+
+C<Set($EmailSubjectTagRegex, qr/(example.com|example.org)/i );>
+
+This setting would make RT behave exactly as it does without the
+setting enabled.
+
+=cut
+
+#Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i );
+
+
+
+=item C<$Organization>
+
+You should set this to your organization's DNS domain. For example,
+I<fsck.com> or I<asylum.arkham.ma.us>. It's used by the linking interface to
+guarantee that ticket URIs are unique and easy to construct.
+
+=cut
+
+Set($Organization , "example.com");
+
+=item C<$MinimumPasswordLength>
+
+C<$MinimumPasswordLength> defines the minimum length for user
+passwords. Setting it to 0 disables this check.
+
+=cut
+
+Set($MinimumPasswordLength , "5");
+
+=item C<$Timezone>
+
+C<$Timezone> is used to convert times entered by users into GMT and back again
+It should be set to a timezone recognized by your local unix box.
+
+=cut
+
+Set($Timezone , 'US/Eastern');
+
+=back
+
+=head1 Database Configuration
+
+=over 4
+
+=item C<$DatabaseType>
+
+Database driver being used; case matters.
+
+Valid types are "mysql", "Oracle" and "Pg"
+
+=cut
+
+Set($DatabaseType , 'SQLite');
+
+=item C<$DatabaseHost>, C<$DatabaseRTHost>
+
+The domain name of your database server.
+
+If you're running mysql and it's on localhost,
+leave it blank for enhanced performance
+
+=cut
+
+Set($DatabaseHost , 'localhost');
+Set($DatabaseRTHost , 'localhost');
+
+=item C<$DatabasePort>
+
+The port that your database server is running on. Ignored unless it's
+a positive integer. It's usually safe to leave this blank
+
+=cut
+
+Set($DatabasePort , '');
+
+=item C<$DatabaseUser>
+
+The name of the database user (inside the database)
+
+=cut
+
+Set($DatabaseUser , 'rt_user');
+
+=item C<$DatabasePassword>
+
+Password the C<$DatabaseUser> should use to access the database
+
+=cut
+
+Set($DatabasePassword , 'rt_pass');
+
+=item C<$DatabaseName>
+
+The name of the RT's database on your database server
+
+=cut
+
+Set($DatabaseName , 'rt3');
+
+=item C<$DatabaseRequireSSL>
+
+If you're using Postgres and have compiled in SSL support,
+set C<$DatabaseRequireSSL> to 1 to turn on SSL communication
+
+=cut
+
+Set($DatabaseRequireSSL , undef);
+
+=back
+
+=head1 Incoming Mail Gateway Configuration
+
+=over 4
+
+=item C<$OwnerEmail>
+
+C<$OwnerEmail> is the address of a human who manages RT. RT will send
+errors generated by the mail gateway to this address. This address
+should _not_ be an address that's managed by your RT instance.
+
+=cut
+
+Set($OwnerEmail , 'root');
+
+=item C<$LoopsToRTOwner>
+
+If C<$LoopsToRTOwner> is defined, RT will send mail that it believes
+might be a loop to C<$OwnerEmail>
+
+=cut
+
+Set($LoopsToRTOwner , 1);
+
+=item C<$StoreLoops>
+
+If C<$StoreLoops> is defined, RT will record messages that it believes
+to be part of mail loops.
+
+As it does this, it will try to be careful not to send mail to the
+sender of these messages
+
+=cut
+
+Set($StoreLoops , undef);
+
+=item C<$MaxAttachmentSize>
+
+C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored
+in the database.
+
+For mysql and oracle, we set this size at 10 megabytes.
+If you're running a postgres version earlier than 7.1, you will need
+to drop this to 8192. (8k)
+
+=cut
+
+
+Set($MaxAttachmentSize , 10000000);
+
+=item C<$TruncateLongAttachments>
+
+C<$TruncateLongAttachments>: if this is set to a non-undef value,
+RT will truncate attachments longer than C<$MaxAttachmentSize>.
+
+=cut
+
+Set($TruncateLongAttachments , undef);
+
+=item C<$DropLongAttachments>
+
+C<$DropLongAttachments>: if this is set to a non-undef value,
+RT will silently drop attachments longer than C<MaxAttachmentSize>.
+
+=cut
+
+Set($DropLongAttachments , undef);
+
+=item C<$ParsenewMessageForTicketCcs>
+
+If C<$ParseNewMessageForTicketCcs> is true, RT will attempt to divine
+Ticket 'Cc' watchers from the To and Cc lines of incoming messages
+Be forewarned that if you have _any_ addresses which forward mail to
+RT automatically and you enable this option without modifying
+C<$RTAddressRegexp> below, you will get yourself into a heap of trouble.
+
+=cut
+
+Set($ParseNewMessageForTicketCcs , undef);
-# This regexp controls what subject tags RT recognizes as its own.
-# If you're not dealing with historical $rtname values, you'll likely
-# never have to enable this feature.
-#
-# Be VERY CAREFUL with it. Note that it overrides $rtname for subject
-# token matching and that you should use only "non-capturing" parenthesis
-# grouping. For example:
-#
-# set($EmailsubjectTagRegex, qr/(?:example.com|example.org)/i );
-#
-# and NOT
-#
-# set($EmailsubjectTagRegex, qr/(example.com|example.org)/i );
-#
-# This setting would make RT behave exactly as it does without the
-# setting enabled.
-#
-# set($EmailsubjectTagRegex, qr/\Q$rtname\E/i );
+=item C<$RTAddressRegexp>
-# You should set this to your organization's DNS domain. For example,
-# fsck.com or asylum.arkham.ma.us. It's used by the linking interface to
-# guarantee that ticket URIs are unique and easy to construct.
+C<$RTAddressRegexp> is used to make sure RT doesn't add itself as a ticket CC if
+the setting above is enabled.
-set( $organization, "example.com" );
+=cut
+
+Set($RTAddressRegexp , '^rt\@example.com$');
+
+=item C<$CanonicalizeEmailAddressMatch>, C<$CanonicalizeEmailAddressReplace>
+
+RT provides functionality which allows the system to rewrite
+incoming email addresses. In its simplest form,
+you can substitute the value in $<CanonicalizeEmailAddressReplace>
+for the value in $<CanonicalizeEmailAddressMatch>
+(These values are passed to the $<CanonicalizeEmailAddress> subroutine in
+ F<RT/User.pm>)
+
+By default, that routine performs a C<s/$Match/$Replace/gi> on any address
+passed to it.
+
+=cut
+
+#Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$');
+#Set($CanonicalizeEmailAddressReplace , '@example.com');
+
+=item C<$CanonicalizeEmailAddressMatch>
+
+Set this to true and the create new user page will use the values that you
+enter in the form but use the function CanonicalizeUserInfo in
+F<RT/User_Local.pm>
+
+=cut
+
+Set($CanonicalizeOnCreate, 0);
+
+=item C<$SenderMustExistInExternalDatabase>
+
+If C<$SenderMustExistInExternalDatabase> is true, RT will refuse to
+create non-privileged accounts for unknown users if you are using
+the C<$LookupSenderInExternalDatabase> option.
+Instead, an error message will be mailed and RT will forward the
+message to C<$RTOwner>.
+
+If you are not using C<$LookupSenderInExternalDatabase>, this option
+has no effect.
+
+If you define an AutoRejectRequest template, RT will use this
+template for the rejection message.
+
+=cut
+
+Set($SenderMustExistInExternalDatabase , undef);
+
+=item C<@MailPlugins>
+
+C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
+to use; see L<rt-mailgate>
+
+=cut
+
+=item C<$UnsafeEmailCommands>
+
+C<$UnsafeEmailCommands>, if set to true, enables 'take' and 'resolve'
+as possible actions via the mail gateway. As its name implies, this
+is very unsafe, as it allows email with a forged sender to possibly
+resolve arbitrary tickets!
+
+=cut
+
+=item C<$ExtractSubjectTagMatch>, C<$ExtractSubjectTagNoMatch>
+
+The default "extract remote tracking tags" scrip settings; these
+detect when your RT is talking to another RT, and adjusts the
+subject accordingly.
+
+=cut
+
+Set($ExtractSubjectTagMatch, qr/\[.+? #\d+\]/);
+Set($ExtractSubjectTagNoMatch, ( ${RT::EmailSubjectTagRegex}
+ ? qr/\[(?:${RT::EmailSubjectTagRegex}) #\d+\]/
+ : qr/\[\Q$RT::rtname\E #\d+\]/));
+
+=back
+
+=head1 Outgoing Mail Configuration
+
+=over 4
+
+=item C<$MailCommand>
+
+C<$MailCommand> defines which method RT will use to try to send mail.
+We know that 'sendmailpipe' works fairly well. If 'sendmailpipe'
+doesn't work well for you, try 'sendmail'. Other options are 'smtp'
+or 'qmail'.
+
+Note that you should remove the '-t' from C<$SendmailArguments>
+if you use 'sendmail' rather than 'sendmailpipe'
+
+=cut
+
+Set($MailCommand , 'sendmailpipe');
+
+=back
+
+=head1 Sendmail Configuration
+
+These options only take effect if C<$MailCommand> is 'sendmail' or
+'sendmailpipe'
+
+=over 4
+
+=item C<$SendmailArguments>
+
+C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
+If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
+These options are good for most sendmail wrappers and workalikes
+
+These arguments are good for sendmail brand sendmail 8 and newer
+C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
+
+=cut
+
+Set($SendmailArguments , "-oi -t");
+
+
+=item C<$SendmailBounceArguments>
+
+C<$SendmailBounceArguments> defines what flags to pass to C<$Sendmail>
+assuming RT needs to send an error (ie. bounce).
+
+=cut
+
+Set($SendmailBounceArguments , '-f "<>"');
+
+=item C<$SendmailPath>
-# $MinimumpasswordLength defines the minimum length for user
-# passwords. setting it to 0 disables this check
-set( $MinimumpasswordLength, "5" );
+If you selected 'sendmailpipe' above, you MUST specify the path to
+your sendmail binary in C<$SendmailPath>.
-# $timezone is used to convert times entered by users into GMT and back again
-# It should be set to a timezone recognized by your local unix box.
-set( $timezone, 'US/Eastern' );
+=cut
+
+Set($SendmailPath , "/usr/sbin/sendmail");
-# }}}
-# {{{ Database Configuration
+=back
-# Database driver being used; case matters. Valid types are "mysql",
-# "Oracle" and "Pg"
+=head1 SMTP Configuration
-set( $DatabaseType, 'mysql' );
+These options only take effect if C<$MailCommand> is 'smtp'
-# The domain name of your database server
-# If you're running mysql and it's on localhost,
-# leave it blank for enhanced performance
-set( $DatabaseHost, 'localhost' );
-set( $DatabaseRTHost, 'localhost' );
+=over 4
-# The port that your database server is running on. Ignored unless it's
-# a positive integer. It's usually safe to leave this blank
-set( $DatabasePort, '' );
+=item C<$SMTPServer>
-#The name of the database user (inside the database)
-set( $DatabaseUser, 'rt_user' );
+C<$SMTPServer> should be set to the hostname of the SMTP server to use
-# password the DatabaseUser should use to access the database
-set( $Databasepassword, 'rt_pass' );
+=cut
-# The name of the RT's database on your database server
-set( $Databasename, 'rt3' );
+Set($SMTPServer, undef);
-# If you're using Postgres and have compiled in SSL support,
-# set DatabaseRequireSSL to 1 to turn on SSL communication
-set( $DatabaseRequireSSL, undef );
+=item C<$SMTPFrom>
-# }}}
+C<$SMTPFrom> should be set to the 'From' address to use, if not the
+email's 'From'
-# {{{ Incoming mail gateway configuration
+=cut
-# OwnerEmail is the address of a human who manages RT. RT will send
-# errors generated by the mail gateway to this address. This address
-# should _not_ be an address that's managed by your RT instance.
+Set($SMTPFrom, undef);
-set( $OwnerEmail, 'root' );
+=item C<$SMTPDebug>
-# If $LoopsToRTOwner is defined, RT will send mail that it believes
-# might be a loop to $OwnerEmail
+C<$SMTPDebug> should be set to true to debug SMTP mail sending
-set( $LoopsToRTOwner, 1 );
+=cut
-# If $StoreLoops is defined, RT will record messages that it believes
-# to be part of mail loops.
-# As it does this, it will try to be careful not to send mail to the
-# sender of these messages
+Set($SMTPDebug, 0);
-set( $StoreLoops, undef );
+=back
-# $MaxAttachmentSize sets the maximum size (in bytes) of attachments stored
-# in the database.
+=head1 Other Mailer Configuration
-# For mysql and oracle, we set this size at 10 megabytes.
-# If you're running a postgres version earlier than 7.1, you will need
-# to drop this to 8192. (8k)
+=over 4
-set( $MaxAttachmentSize, 10000000 );
+=item C<@MailParams>
-# $TruncateLongAttachments: if this is set to a non-undef value,
-# RT will truncate attachments longer than MaxAttachmentSize.
+C<@MailParams> defines a list of options passed to $MailCommand if it
+is not 'sendmailpipe', 'sendmail', or 'smtp'
-set( $TruncateLongAttachments, undef );
+=cut
-# $DropLongAttachments: if this is set to a non-undef value,
-# RT will silently drop attachments longer than MaxAttachmentSize.
+Set(@MailParams, ());
-set( $DropLongAttachments, undef );
+=item C<$CorrespondAddress>, C<$CommentAddress>
-# If $ParseNewMessageForTicketCcs is true, RT will attempt to divine
-# Ticket 'Cc' watchers from the To and Cc lines of incoming messages
-# Be forewarned that if you have _any_ addresses which forward mail to
-# RT automatically and you enable this option without modifying
-# "RTAddressRegexp" below, you will get yourself into a heap of trouble.
+RT is designed such that any mail which already has a ticket-id associated
+with it will get to the right place automatically.
-set( $ParseNewMessageForTicketCcs, undef );
+C<$CorrespondAddress> and C<$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.
-# RTAddressRegexp is used to make sure RT doesn't add itself as a ticket CC if
-# the setting above is enabled.
+=cut
-set( $RTAddressRegexp, '^rt\@example.com$' );
+Set($CorrespondAddress , '');
-# RT provides functionality which allows the system to rewrite
-# incoming email addresses. In its simplest form,
-# you can substitute the value in canonicalize_emailReplace
-# for the value in canonicalize_emailMatch
-# (These values are passed to the canonicalize_email subroutine in RT/User.pm)
-# By default, that routine performs a s/$Match/$Replace/gi on any address passed to it
+Set($CommentAddress , '');
-#set($canonicalize_emailMatch , '@subdomain\.example\.com$');
-#set($canonicalize_emailReplace , '@example.com');
+=item C<UseFriendlyFromLine>
-# set this to true and the create new user page will use the values that you
-# enter in the form but use the function canonicalize_UserInfo in User_Local.pm
-set( $canonicalize_OnCreate, 0 );
+By default, RT sets the outgoing mail's "From:" header to
+"SenderName via RT". Setting C<$UseFriendlyFromLine> to 0 disables it.
-# If $SenderMustExistInExternalDatabase is true, RT will refuse to
-# create non-privileged accounts for unknown users if you are using
-# the "LookupSenderInExternalDatabase" option.
-# Instead, an error message will be mailed and RT will forward the
-# message to $RTOwner.
-#
-# If you are not using $LookupSenderInExternalDatabase, this option
-# has no effect.
-#
-# If you define an AutoRejectRequest template, RT will use this
-# template for the rejection message.
+=cut
-set( $SenderMustExistInExternalDatabase, undef );
+Set($UseFriendlyFromLine, 1);
-# @MailPlugins is a list of auth plugins for L<RT::Interface::Email>
-# to use; see L<rt-mailgate>
-set( @MailPlugins, 'Auth::MailFrom' );
+=item C<$FriendlyFromLineFormat>
-# $UnsafeEmailCommands, if set to true, enables 'take' and 'resolve'
-# as possible actions via the mail gateway. As its name implies, this
-# is very unsafe, as it allows email with a forged sender to possibly
-# resolve arbitrary tickets!
+C<sprintf()> format of the friendly 'From:' header; its arguments
+are SenderName and SenderEmailAddress.
-# }}}
+=cut
+
+Set($FriendlyFromLineFormat, "\"%s via RT\" <%s>");
+
+=item C<$UseFriendlyToLine>
+
+RT can optionally set a "Friendly" 'To:' header when sending messages to
+Ccs or AdminCcs (rather than having a blank 'To:' header.
+
+This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL
+If you are using sendmail, rather than postfix, qmail, exim or some other MTA,
+you _must_ disable this option.
+
+=cut
-# {{{ Outgoing mail configuration
+Set($UseFriendlyToLine, 0);
-# $MailCommand defines which method RT will use to try to send mail.
-# We know that 'sendmailpipe' works fairly well. If 'sendmailpipe'
-# doesn't work well for you, try 'sendmail'. Other options are 'smtp'
-# or 'qmail'.
-#
-# Note that you should remove the '-t' from $SendmailArguments
-# if you use 'sendmail' rather than 'sendmailpipe'
+=item C<$FriendlyToLineFormat>
-set( $MailCommand, 'sendmailpipe' );
+C<sprintf()> format of the friendly 'From:' header; its arguments
+are WatcherType and TicketId.
-# {{{ Sendmail Configuration
-# These options only take effect if $MailCommand is 'sendmail' or
-# 'sendmailpipe'
+=cut
-# $SendmailArguments defines what flags to pass to $SendmailPath
-# If you picked 'sendmailpipe', you MUST add a -t flag to $SendmailArguments
-# These options are good for most sendmail wrappers and workalikes
-set( $SendmailArguments, "-oi -t" );
+Set($FriendlyToLineFormat, "\"%s of ". RT->Config->Get('rtname') ." Ticket #%s\":;");
-# These arguments are good for sendmail brand sendmail 8 and newer
-#set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");
+=item C<$NotifyActor>
-# $SendmailBounceArguments defines what flags to pass to $Sendmail
-# assuming RT needs to send an error (ie. bounce).
-set( $SendmailBounceArguments, '-f "<>"' );
+By default, RT doesn't notify the person who performs an update, as they
+already know what they've done. If you'd like to change this behaviour,
+Set C<$NotifyActor> to 1
-# If you selected 'sendmailpipe' above, you MUST specify the path to
-# your sendmail binary in $SendmailPath.
-set( $SendmailPath, "/usr/sbin/sendmail" );
+=cut
-# }}}
+Set($NotifyActor, 0);
-# {{{ SMTP configuration
-# These options only take effect if $MailCommand is 'smtp'
+=item C<$RecordOutgoingEmail>
-# $SMTPServer should be set to the hostname of the SMTP server to use
-set( $SMTPServer, undef );
+By default, RT records each message it sends out to its own internal database.
+To change this behavior, set C<$RecordOutgoingEmail> to 0
-# $SMTPFrom should be set to the 'From' address to use, if not the
-# email's 'From'
-set( $SMTPFrom, undef );
+=cut
-# $SMTPDebug should be set to true to debug SMTP mail sending
-set( $SMTPDebug, 0 );
+Set($RecordOutgoingEmail, 1);
-# }}}
+=item C<$VERPPrefix>, C<$VERPPrefix>
-# {{{ Other mailer configuration
-# @MailParams defines a list of options passed to $MailCommand if it
-# is not 'sendmailpipe', 'sendmail', or 'smtp'
-set( @MailParams, () );
+VERP support (http://cr.yp.to/proto/verp.txt)
-# }}}
+uncomment the following two directives to generate envelope senders
+of the form C<${VERPPrefix}${originaladdress}@${VERPDomain}>
+(i.e. rt-jesse=fsck.com at rt.example.com ).
-# RT is designed such that any mail which already has a ticket-id associated
-# with it will get to the right place automatically.
+This currently only works with sendmail and sendmailppie.
-# $correspond_address and $comment_address 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.
+=cut
-set( $correspond_address, 'rt_correspond_address_not_set' );
+# Set($VERPPrefix, 'rt-');
+# Set($VERPDomain, $RT::Organization);
-set( $comment_address, 'rt_comment_address_not_set' );
-# By default, RT sets the outgoing mail's "From:" header to
-# "Sendername via RT". setting this option to 0 disables it.
+=item C<$ForwardFromUser>
-set( $UseFriendlyFromLine, 1 );
+By default, RT forwards a message using queue's address and adds RT's tag into
+subject of the outgoing message, so recipients' replies go into RT as correspondents.
-# sprintf() format of the friendly 'From:' header; its arguments
-# are Sendername and Senderemail.
-set( $friendly_from_line_format, "\"%s via RT\" <%s>" );
+To change this behavior, set C<$ForwardFromUser> to true value and RT will use
+address of the current user and leave subject without RT's tag.
-# RT can optionally set a "Friendly" 'To:' header when sending messages to
-# Ccs or AdminCcs (rather than having a blank 'To:' header.
+=cut
-# This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL
-# If you are using sendmail, rather than postfix, qmail, exim or some other MTA,
-# you _must_ disable this option.
+Set($ForwardFromUser, 0);
-set( $UseFriendlyToLine, 0 );
+=item C<$ShowBccHeader>
-# sprintf() format of the friendly 'From:' header; its arguments
-# are WatcherType and TicketId.
-set( $friendly_to_line_format, "\"%s of " . RT->config->get('rtname') . " Ticket #%s\":;" );
+By default RT hides from the web UI information about blind copies user sent on
+reply or comment.
-# By default, RT doesn't notify the person who performs an update, as they
-# already know what they've done. If you'd like to change this behaviour,
-# set $NotifyActor to 1
+To change this set the following option to true value.
-set( $NotifyActor, 0 );
+=cut
-# By default, RT records each message it sends out to its own internal database.
-# To change this behavior, set $RecordOutgoingEmail to 0
+Set($ShowBccHeader, 0);
-set( $RecordOutgoingEmail, 1 );
+=back
-# VERP support (http://cr.yp.to/proto/verp.txt)
-# uncomment the following two directives to generate envelope senders
-# of the form ${VERPPrefix}${originaladdress}@${VERPDomain}
-# (i.e. rt-jesse=fsck.com at rt.example.com ) This currently only works
-# with sendmail and sendmailppie.
-# set($VERPPrefix, 'rt-');
-# set($VERPDomain, $RT::organization);
+=head1 GnuPG Configuration
-# By default, RT forwards a message using queue's address and adds RT's tag into
-# subject of the outgoing message, so recipients' replies go into RT as correspondents.
-# To change this behavior, set $ForwardFromUser to 0 and RT will use address of the
-# current user and leave subject without RT's tag.
+A full description of the (somewhat extensive) GnuPG integration can be found
+by running the command `perldoc L<RT::Crypt::GnuPG>` (or `perldoc
+ lib/RT/Crypt/GnuPG.pm` from your RT install directory).
-set( $ForwardFromUser, 0 );
+=over 4
-# }}}
+=item C<%GnuPG>
-# {{{ GnuPG
-# A full description of the (somewhat extensive) GnuPG integration can be found by
-# running the command
-#
-# perldoc RT::Crypt::GnuPG (or perldoc lib/RT/Crypt/GnuPG.pm from your RT install directory).
+Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and
+signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
-set(%GnuPG,
- enable => 1,
+If you want to allow people to encrypt attachments inside the DB then
+set C<AllowEncryptDataInDB> to true
- # set outgoing_messages_format to 'inline' to use inline encryption and
- # signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
- outgoing_messages_format => 'RFC', # Inline
+=cut
- # If you want to allow people to encrypt attachments inside the DB then
- # set below option to true value
- AllowEncryptDataInDB => 0,
+Set( %GnuPG,
+ Enable => 1,
+ OutgoingMessagesFormat => 'RFC', # Inline
+ AllowEncryptDataInDB => 0,
);
-# Options of GnuPG program
-# If you override this in your RT_SiteConfig, you should be sure
-# to include a homedir setting
-# NOTE that options with '-' character MUST be quoted.
+=item C<%GnuPGOptions>
+
+Options of GnuPG program.
-set(%GnuPGOptions,
+If you override this in your RT_SiteConfig, you should be sure
+to include a homedir setting.
+
+NOTE that options with '-' character MUST be quoted.
+
+=cut
+
+Set(%GnuPGOptions,
homedir => '/home/jesse/svk/3.999-DANGEROUS/var/data/gpg',
- # URL of a keyserver
- # keyserver => 'hkp://subkeys.pgp.net',
+# URL of a keyserver
+# keyserver => 'hkp://subkeys.pgp.net',
- # enables the automatic retrieving of keys when encrypting
- # 'auto-key-locate' => 'keyserver',
+# enables the automatic retrieving of keys when encrypting
+# 'auto-key-locate' => 'keyserver',
- # enables the automatic retrieving of keys when verifying signatures
- # 'auto-key-retrieve' => undef,
+# enables the automatic retrieving of keys when verifying signatures
+# 'auto-key-retrieve' => undef,
);
-# }}}
-# {{{ Logging
+=back
+
+=head1 Logging Configuration
+
+The default is to log anything except debugging
+information to syslog. Check the L<Log::Dispatch> POD for
+information about how to get things by syslog, mail or anything
+else, get debugging info in the log, etc.
+
+It might generally make sense to send error and higher by email to
+some administrator. If you do this, be careful that this email
+isn't sent to this RT instance. Mail loops will generate a critical
+log message.
+
+=over 4
+
+=item C<$LogToSyslog>, C<$LogToScreen>
+
+The minimum level error that will be logged to the specific device.
+From lowest to highest priority, the levels are:
+ debug info notice warning error critical alert emergency
+
+=cut
+
+Set($LogToSyslog , 'debug');
+Set($LogToScreen , 'info');
+
+=item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
+
+Logging to a standalone file is also possible, but note that the
+file should needs to both exist and be writable by all direct users
+of the RT API. This generally include the web server, whoever
+rt-crontool runs as. Note that as rt-mailgate and the RT CLI go
+through the webserver, so their users do not need to have write
+permissions to this file. If you expect to have multiple users of
+the direct API, Best Practical recommends using syslog instead of
+direct file logging.
+
+=cut
+
+Set($LogToFile , undef);
+Set($LogDir, '/home/jesse/svk/3.999-DANGEROUS/var/log');
+Set($LogToFileNamed , "rt.log"); #log to rt.log
+
+=item C<$LogStackTraces>
+
+If set to a log level then logging will include stack
+traces for messages with level equal to or greater than
+specified.
+
+=cut
+
+Set($LogStackTraces, '');
+
+=item C<@LogToSyslogConf>
+
+On Solaris or UnixWare, set to ( socket => 'inet' ). Options here
+override any other options RT passes to L<Log::Dispatch::Syslog>.
+Other interesting flags include facility and logopt. (See the
+L<Log::Dispatch::Syslog> documentation for more information.) (Maybe
+ident too, if you have multiple RT installations.)
+
+=cut
+
+Set(@LogToSyslogConf, ());
+
+=item C<$StatementLog>,
+
+RT has rudimentary SQL statement logging support if you have
+DBIx-SearchBuilder 1.31_1 or higher; simply set C<$StatementLog> to be
+the level that you wish SQL statements to be logged at.
+
+=cut
+
+Set($StatementLog, undef);
+
+=back
+
+=head1 Web Interface Configuration
+
+=over 4
+
+=item C<$WebDefaultStylesheet>
+
+This determines the default stylesheet the RT web interface will use.
+RT ships with two valid values by default:
-# Logging. The default is to log anything except debugging
-# information to syslog. Check the Log::Dispatch POD for
-# information about how to get things by syslog, mail or anything
-# else, get debugging info in the log, etc.
+ 3.5-default The totally new, default layout for RT 3.5
+ 3.4-compat A 3.4 compatibility stylesheet to make RT 3.5 look
+ (mostly) like 3.4
-# It might generally make sense to send error and higher by email to
-# some administrator. If you do this, be careful that this email
-# isn't sent to this RT instance. Mail loops will generate a critical
-# log message.
+This value actually specifies a directory in F<share/html/NoAuth/css/>
+from which RT will try to load the file main.css (which should
+ at import any other files the stylesheet needs). This allows you to
+easily and cleanly create your own stylesheets to apply to RT. This
+option can be overridden by users in their preferences.
-# The minimum level error that will be logged to the specific device.
-# From lowest to highest priority, the levels are:
-# debug info notice warning error critical alert emergency
-set( $LogToSyslog, 'debug' );
-set( $LogToScreen, 'error' );
+=cut
+
+Set($WebDefaultStylesheet, 'web2');
+
+=item C<$UsernameFormat>
+
+This determines how user info is displayed. Concise will show one of
+either NickName, RealName, Name or EmailAddress, depending on what exists
+and whether the user is privileged or not. Verbose will show RealName and
+EmailAddress.
+
+=cut
+
+ Set($UsernameFormat, 'concise');
+
+
+=item C<$WebPath>
+
+If you're putting the web ui somewhere other than at the root of
+your server, you should set C<$WebPath> to the path you'll be
+serving RT at.
+
+C<$WebPath> requires a leading / but no trailing /.
+
+In most cases, you should leave C<$WebPath> set to '' (an empty value).
+
+=cut
+
+Set($WebPath, "");
+
+=item C<$WebPort>
+
+If we're running as a superuser, run on port 80
+Otherwise, pick a high port for this user.
+
+=cut
+
+Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
+
+=item C<$WebDomain>
+
+you know what domain name is, right? ;)
+
+=cut
+
+Set( $WebDomain, 'localhost' );
+
+=item C<$WebBaseURL>, C<$WebURL>
+
+This is the Scheme, server and port for constructing urls to webrt
+C<$WebBaseURL> doesn't need a trailing /
+
+=cut
+
+Set($WebBaseURL, 'http://' . RT->Config->Get('WebDomain') . ':' . RT->Config->Get('WebPort'));
+
+Set($WebURL, RT->Config->Get('WebBaseURL') . RT->Config->Get('WebPath') . "/");
+
+=item C<$WebImagesURL>
+
+C<$WebImagesURL> points to the base URL where RT can find its images.
+Define the directory name to be used for images in rt web
+documents.
+
+=cut
+
+Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/");
+
+=item C<$LogoURL>
+
+C<$LogoURL> points to the URL of the RT logo displayed in the web UI
+
+=cut
+
+Set($LogoURL, $Config->Get('WebImagesURL') . "bplogo.gif");
+
+=item C<$WebNoAuthRegex>
+
+What portion of RT's URLspace should not require authentication.
+
+=cut
+
+Set($WebNoAuthRegex, qr{^ (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x );
+
+=item C<$MessageBoxWidth>, C<$MessageBoxHeight>
+
+For message boxes, set the entry box width, height and what type of
+wrapping to use. These options can be overridden by users in their
+preferences.
+
+Default width: 72, height: 15
+
+=cut
+
+Set($MessageBoxWidth, 72);
+Set($MessageBoxHeight, 15);
+
+=item C<$MessageBoxWrap>
+
+Default wrapping: "HARD" (choices "SOFT", "HARD")
+
+=cut
+
+Set($MessageBoxWrap, "HARD");
+
+=item C<$MessageBoxRichText>
+
+Should "rich text" editing be enabled? This option lets your users send html email messages from the web interface.
-# Logging to a standalone file is also possible, but note that the
-# file should needs to both exist and be writable by all direct users
-# of the RT API. This generally include the web server, whoever
-# rt-crontool runs as. Note that as rt-mailgate and the RT CLI go
-# through the webserver, so their users do not need to have write
-# permissions to this file. If you expect to have multiple users of
-# the direct API, Best Practical recommends using syslog instead of
-# direct file logging.
+=cut
+
+Set($MessageBoxRichText, 1);
+
+=item C<$WikiImplicitLinks>
+
+Support implicit links in WikiText custom fields? A true value
+causes InterCapped or ALLCAPS words in WikiText fields to
+automatically become links to searches for those words. If used on
+RTFM articles, it links to the RTFM article with that name.
+
+=cut
+
+Set($WikiImplicitLinks, 0);
+
+=item C<$TrustHTMLAttachments>
+
+if C<TrustHTMLAttachments> is not defined, we will display them
+as text. This prevents malicious HTML and javascript from being
+sent in a request (although there is probably more to it than that)
+
+=cut
+
+Set($TrustHTMLAttachments, undef);
+
+=item C<$RedistributeAutoGeneratedMessages>
+
+Should RT redistribute correspondence that it identifies as
+machine generated? A true value will do so; setting this to '0'
+will cause no such messages to be redistributed.
+You can also use 'privileged' (the default), which will redistribute
+only to privileged users. This helps to protect against malformed
+bounces and loops caused by autocreated requestors with bogus addresses.
+
+=cut
-set( $LogToFile, undef );
-set( $LogDir, '/home/jesse/svk/3.999-DANGEROUS/var/log' );
-set( $LogToFilenamed, "rt.log" ); #log to rt.log
+Set($RedistributeAutoGeneratedMessages, 'privileged');
-# If set to a log level then logging will include stack
-# traces for messages with level equal to or greater than
-# specified.
+=item C<$PreferRichText>
-set( $LogStackTraces, '' );
+If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
+messages in preference to their plaintext alternatives. RT "scrubs" the
+html to show only a minimal subset of HTML to avoid possible contamination
+by cross-site-scripting attacks.
-# On Solaris or UnixWare, set to ( socket => 'inet' ). Options here
-# override any other options RT passes to Log::Dispatch::Syslog.
-# Other interesting flags include facility and logopt. (See the
-# Log::Dispatch::Syslog documentation for more information.) (Maybe
-# ident too, if you have multiple RT installations.)
+=cut
-set( @LogToSyslogConf, () );
+Set($PreferRichText, undef);
-# RT has rudimentary SQL statement logging support if you have
-# DBIx-SearchBuilder 1.31_1 or higher; simply set $StatementLog to be
-# the level that you wish SQL statements to be logged at.
-set( $StatementLog, undef );
+=item C<$WebExternalAuth>
-# }}}
+If C<$WebExternalAuth> is defined, RT will defer to the environment's
+REMOTE_USER variable.
-# {{{ Web interface configuration
+=cut
-# This determines the default stylesheet the RT web interface will use.
-# RT ships with two valid values by default:
-#
-# 3.5-default The totally new, default layout for RT 3.5
-# 3.4-compat A 3.4 compatibility stylesheet to make RT 3.5 look
-# (mostly) like 3.4
-#
-# This value actually specifies a directory in share/html/NoAuth/css/
-# from which RT will try to load the file main.css (which should
-# @import any other files the stylesheet needs). This allows you to
-# easily and cleanly create your own stylesheets to apply to RT. This
-# option can be overridden by users in their preferences.
-set( $WebDefaultStylesheet, '3.5-default' );
+Set($WebExternalAuth, undef);
-# Define the directory name to be used for images in rt web
-# documents.
+=item C<$WebFallbackToInternalAuth>
-# 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.
-# $WebPath requires a leading / but no trailing /.
-#
-# In most cases, you should leave $WebPath set to '' (an empty value).
+If C<$WebFallbackToInternalAuth> is undefined, the user is allowed a chance
+of fallback to the login screen, even if REMOTE_USER failed.
-set( $WebPath, "" );
+=cut
-# If we're running as a superuser, run on port 80
-# Otherwise, pick a high port for this user.
+Set($WebFallbackToInternalAuth , undef);
-set( $WebPort, 80 ); # + ($< * 7274) % 32766 + ($< && 1024));
+=item C<$WebExternalGecos>
-# This is the Scheme, server and port for constructing urls to webrt
-# $WebbaseURL doesn't need a trailing /
+C<$WebExternalGecos> means to match 'gecos' field as the user identity);
+useful with mod_auth_pwcheck and IIS Integrated Windows logon.
-set( $WebbaseURL, "http://localhost:" . RT->config->get('WebPort') );
+=cut
-set( $WebURL, RT->config->get('WebbaseURL') . RT->config->get('WebPath') . "/" );
+Set($WebExternalGecos , undef);
-# $WebImagesURL points to the base URL where RT can find its images.
+=item C<$WebExternalAuto>
-set( $WebImagesURL, RT->config->get('WebPath') . "/NoAuth/images/" );
+C<$WebExternalAuto> will create users under the same name as REMOTE_USER
+upon login, if it's missing in the Users table.
-# $LogoURL points to the URL of the RT logo displayed in the web UI
+=cut
-set( $LogoURL, $Config->get('WebImagesURL') . "bplogo.gif" );
+Set($WebExternalAuto , undef);
-# WebNoAuthRegex - What portion of RT's URLspace should not require
-# authentication.
-set( $WebNoAuthRegex, qr{^ (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x );
+=item C<$AutoCreate>
-# For message boxes, set the entry box width, height and what type of
-# wrapping to use. These options can be overridden by users in their
-# preferences.
-#
-# Default width: 72, height: 15
-set( $MessageBoxWidth, 72 );
-set( $MessageBoxHeight, 15 );
+If C<$WebExternalAuto> is true, C<$AutoCreate> will be passed to User's
+Create method. Use it to set defaults, such as creating
+Unprivileged users with C<{ Privileged => 0 }>
+( Must be a hashref of arguments )
-# Default wrapping: "HARD" (choices "SOFT", "HARD")
-set( $MessageBoxWrap, "HARD" );
+=cut
-# Support implicit links in WikiText custom fields? A true value
-# causes InterCapped or ALLCAPS words in WikiText fields to
-# automatically become links to searches for those words. If used on
-# RTFM articles, it links to the RTFM article with that name.
-set( $WikiImplicitLinks, 0 );
+Set($AutoCreate, undef);
-# if TrustHTMLAttachments is not defined, we will display them
-# as text. This prevents malicious HTML and javascript from being
-# sent in a request (although there is probably more to it than that)
-set( $TrustHTMLAttachments, undef );
+=item C<$WebSessionClass>
-# Should RT redistribute correspondence that it identifies as
-# machine generated? A true value will do so; setting this to '0'
-# will cause no such messages to be redistributed.
-# You can also use 'privileged' (the default), which will redistribute
-# only to privileged users. This helps to protect against malformed
-# bounces and loops caused by autoCreated requestors with bogus addresses.
-set( $RedistributeAutoGeneratedMessages, 'privileged' );
+C<$WebSessionClass> is the class you wish to use for managing Sessions.
+It defaults to use your SQL database, but if you are using MySQL 3.x and
+plans to use non-ascii Queue names, uncomment and add this line to
+F<RT_SiteConfig.pm> will prevent session corruption.
-# If PreferRichText is set to a true value, RT will show HTML/Rich text
-# messages in preference to their plaintext alternatives. RT "scrubs" the
-# html to show only a minimal subset of HTML to avoid possible contamination
-# by cross-site-scripting attacks.
-set( $PreferRichText, undef );
+=cut
-# If $WebExternalAuth is defined, RT will defer to the environment's
-# REMOTE_USER variable.
+# Set($WebSessionClass , 'Apache::Session::File');
-set( $WebExternalAuth, undef );
+=item C<$AutoLogoff>
-# If $WebOpenIdAuth is enabled, RT will allow OpenID logins. New users who present
-# OpenID Credentials will be created as unprivileged users with their OpenID as their name.
-# To enable OpenID Support, you need to install LWPx::ParanoidAgent, Cache::FileCache
-# and Net::OpenID::Consumer.
-#
-set( $WebOpenIdAuth, undef );
+By default, RT's user sessions persist until a user closes his or her
+browser. With the C<$AutoLogoff> option you can setup session lifetime in
+minutes. A user will be logged out if he or she doesn't send any requests
+to RT for the defined time.
-# If $WebFallbackToInternalAuth is undefined, the user is allowed a chance
-# of fallback to the login screen, even if REMOTE_USER failed.
+=cut
-set( $WebFallbackToInternalAuth, undef );
+Set($AutoLogoff, 0);
-# $WebExternalgecos means to match 'gecos' field as the user identity);
-# useful with mod_auth_pwcheck and IIS Integrated Windows logon.
+=item C<$WebSecureCookies>
-set( $WebExternalgecos, undef );
+By default, RT's session cookie isn't marked as "secure" Some web browsers
+will treat secure cookies more carefully than non-secure ones, being careful
+not to write them to disk, only send them over an SSL secured connection
+and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value.
+NOTE: You probably don't want to turn this on _unless_ users are only connecting
+via SSL encrypted HTTP connections.
-# $WebExternalAuto will create users under the same name as REMOTE_USER
-# upon login, if it's missing in the Users table.
+=cut
-set( $WebExternalAuto, undef );
+Set($WebSecureCookies, 0);
-# $AutoCreate is a custom set of attributes to create the user with,
-# if they are Created using $WebExternalAuto
+=item C<$WebFlushDbCacheEveryRequest>
-set( $AutoCreate, undef );
+By default, RT clears its database cache after every page view.
+This ensures that you've always got the most current information
+when working in a multi-process (mod_perl or FastCGI) Environment
+Setting C<$WebFlushDbCacheEveryRequest> to '0' will turn this off,
+which will speed RT up a bit, at the expense of a tiny bit of data
+accuracy.
-# $WebSessionClass is the class you wish to use for managing Sessions.
-# It defaults to use your SQL database, but if you are using MySQL 3.x and
-# plans to use non-ascii queue names, uncomment and add this line to
-# RT_SiteConfig.pm will prevent session corruption.
+=cut
-# set($WebSessionClass , 'Apache::Session::File');
+Set($WebFlushDbCacheEveryRequest, '1');
-# By default, RT hold session unless user close browser application, with
-# $AutoLogoff option you can setup session lifetime in minutes. User
-# would be logged out if he doesn't send any requests to RT for the
-# defined time.
-set( $AutoLogoff, 0 );
+=item C<$MaxInlineBody>
-# By default, RT's session cookie isn't marked as "secure" Some web browsers
-# will treat secure cookies more carefully than non-secure ones, being careful
-# not to write them to disk, only send them over an SSL secured connection
-# and so on. To enable this behaviour, set # $WebSecureCookies to a true value.
-# NOTE: You probably don't want to turn this on _unless_ users are only connecting
-# via SSL encrypted HTTP connections.
+C<$MaxInlineBody> is the maximum attachment size that we want to see
+inline when viewing a transaction. RT will inline any text if value
+is undefined or 0. This option can be overridden by users in their
+preferences.
-set( $WebSecureCookies, 0 );
+=cut
-# By default, RT clears its database cache after every page view.
-# This ensures that you've always got the most current information
-# when working in a multi-process (mod_perl or FastCGI) Environment
-# setting $WebFlushDbCacheEveryRequest to '0' will turn this off,
-# which will speed RT up a bit, at the expense of a tiny bit of data
-# accuracy.
+Set($MaxInlineBody, 12000);
-set( $WebFlushDbCacheEveryRequest, '1' );
+=item C<$DefaultSummaryRows>
-# $MaxInlineBody is the maximum attachment size that we want to see
-# inline when viewing a transaction. RT will inline any text if value
-# is undefined or 0. This option can be overridden by users in their
-# preferences.
+C<$DefaultSummaryRows> is default number of rows displayed in for search
+results on the frontpage.
-set( $MaxInlineBody, 12000 );
+=cut
-# $defaultSummaryRows is default number of rows displayed in for search
-# results on the frontpage.
+Set($DefaultSummaryRows, 10);
-set( $defaultSummaryRows, 10 );
+=item C<$OldestTransactionsFirst>
-# By default, RT shows newest transactions at the bottom of the ticket
-# history page, if you want see them at the top set this to '0'. This
-# option can be overridden by users in their preferences.
+By default, RT shows newest transactions at the bottom of the ticket
+history page, if you want see them at the top set this to '0'. This
+option can be overridden by users in their preferences.
-set( $OldestTransactionsFirst, '1' );
+=cut
-# By default, RT shows images attached to incoming (and outgoing) ticket updates
-# inline. set this variable to 0 if you'd like to disable that behaviour
+Set($OldestTransactionsFirst, '1');
-set( $ShowTransactionImages, 1 );
+=item C<$ShowTransactionImages>
-# $HomepageComponents is an arrayref of allowed components on a user's
-# customized homepage ("RT at a glance").
+By default, RT shows images attached to incoming (and outgoing) ticket updates
+inline. Set this variable to 0 if you'd like to disable that behaviour
-set( $HomepageComponents, [ qw(QuickCreate Quicksearch MyAdminQueues MySupportQueues MyReminders RefreshHomepage) ] );
+=cut
-# @MasonParameters is the list of parameters for the constructor of
-# HTML::Mason's Apache or CGI Handler. This is normally only useful
-# for debugging, eg. profiling individual components with:
-# use MasonX::Profiler; # available on CPAN
-# @MasonParameters = (preamble => 'my $p = MasonX::Profiler->new($m, $r);');
+Set($ShowTransactionImages, 1);
-set( @MasonParameters, () );
-# $defaultSearchResultFormat is the default format for RT search results
-set($defaultSearchResultFormat, qq{
+=item C<$ShowUnreadMessageNotifications>
+
+By default, RT will prompt users when there are new, unread messages on
+tickets they are viewing.
+
+Set C<$ShowUnreadMessageNotifications> to a false value to disable this feature.
+
+=cut
+
+Set($ShowUnreadMessageNotifications, 1);
+
+
+=item C<$HomepageComponents>
+
+C<$HomepageComponents> is an arrayref of allowed components on a user's
+customized homepage ("RT at a glance").
+
+=cut
+
+Set($HomepageComponents, [qw(QuickCreate Quicksearch MyAdminQueues MySupportQueues MyReminders RefreshHomepage)]);
+
+=item C<@MasonParameters>
+
+C<@MasonParameters> is the list of parameters for the constructor of
+HTML::Mason's Apache or CGI Handler. This is normally only useful
+for debugging, eg. profiling individual components with:
+
+ use MasonX::Profiler; # available on CPAN
+ Set(@MasonParameters, (preamble => 'my $p = MasonX::Profiler->new($m, $r);'));
+
+=cut
+
+Set(@MasonParameters, ());
+
+=item C<$DefaultSearchResultFormat>
+
+C<$DefaultSearchResultFormat> is the default format for RT search results
+
+=cut
+
+Set ($DefaultSearchResultFormat, qq{
'<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#',
- '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__subject__</a></B>/TITLE:subject',
+ '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
Status,
- Queuename,
- owner_name,
+ QueueName,
+ OwnerName,
Priority,
'__NEWLINE__',
'',
'<small>__Requestors__</small>',
'<small>__CreatedRelative__</small>',
'<small>__ToldRelative__</small>',
- '<small>__last_updatedRelative__</small>',
- '<small>__time_left__</small>'}
-);
+ '<small>__LastUpdatedRelative__</small>',
+ '<small>__TimeLeft__</small>'});
+
+
+=item C<$SuppressInlineTextFiles>
+
+If C<$SuppressInlineTextFiles> is set to a true value, then uploaded
+text files (text-type attachments with file names) are prevented
+from being displayed in-line when viewing a ticket's history.
+
+=cut
+
+Set($SuppressInlineTextFiles, undef);
-# If $SuppressInlineTextFiles is set to a true value, then uploaded
-# text files (text-type attachments with file names) are prevented
-# from being displayed in-line when viewing a ticket's history.
+=item C<DontSearchFileAttachments>
-set( $SuppressInlineTextFiles, undef );
+If C<$DontSearchFileAttachments> is set to a true value, then uploaded
+files (attachments with file names) are not searched during full-content
+ticket searches.
-# If $DontSearchFileAttachments is set to a true value, then uploaded
-# files (attachments with file names) are not searched during full-content
-# ticket searches.
+=cut
+
+Set($DontSearchFileAttachments, undef);
+
+=item C<$ChartFont>
+
+The L<GD> module (which RT uses for graphs) uses a builtin font that doesn't
+have full Unicode support. You can use a particular TrueType font by setting
+$ChartFont to the absolute path of that font. Your GD library must have
+support for TrueType fonts to use this option.
+
+=cut
+
+Set($ChartFont, undef);
+
+
+=item C<@Active_MakeClicky>
+
+MakeClicky detects various formats of data in headers and email
+messages, and extends them with supporting links. By default, RT
+provides two formats:
+
+* 'httpurl': detects http:// and https:// URLs and adds '[Open URL]'
+ link after the URL.
+
+* 'httpurl_overwrite': also detects URLs as 'httpurl' format, but
+ replace URL with link and *adds spaces* into text if it's longer
+ then 30 chars. This allow browser to wrap long URLs and avoid
+ horizontal scrolling.
+
+See F<share/html/Elements/MakeClicky> for documentation on how to add your own.
+
+=cut
-set( $DontSearchFileAttachments, undef );
+Set(@Active_MakeClicky, qw());
-# The GD module (which RT uses for graphs) uses a builtin font that doesn't
-# have full Unicode support. You can use a particular TrueType font by setting
-# $ChartFont to the absolute path of that font. Your GD library must have
-# support for TrueType fonts to use this option.
+=item C<$DefaultQueue>
-set( $ChartFont, undef );
+Use this to select the default queue name that will be used for creating new
+tickets. You may use either the queue's name or its ID. This only affects the
+queue selection boxes on the web interface.
-# MakeClicky detects various formats of data in headers and email
-# messages, and extends them with supporting links. By default, RT
-# provides two formats:
-#
-# * 'httpurl': detects http:// and https:// URLs and adds '[Open URL]'
-# link after the URL.
-#
-# * 'httpurl_overwrite': also detects URLs as 'httpurl' format, but
-# replace URL with link and *adds spaces* into text if it's longer
-# then 30 chars. This allow browser to wrap long URLs and avoid
-# horizontal scrolling.
-#
-# See html/Elements/MakeClicky for documentation on how to add your own.
-set( @Active_MakeClicky, qw() );
+=cut
+
+#Set($DefaultQueue, 'General');
+
+=back
+
+=head1 L<Net::Server> (rt-server) Configuration
-# }}}
+=over 4
-# {{{ RT UTF-8 settings
+=item C<$StandaloneMinServers>, C<$StandaloneMaxServers>
-# An array that contains Languages supported by RT's internationalization
-# interface. Defaults to all *.po lexicons; setting it to qw(en ja) will make
-# RT bilingual instead of multilingual, but will save some memory.
+The absolute minimum and maximum number of servers that will be created to
+handle requests. Having multiple servers means that serving a slow page will
+affect other users less.
-set( @LexiconLanguages, qw(*) );
+=cut
+
+Set($StandaloneMinServers, 1);
+Set($StandaloneMaxServers, 1);
-# An array that contains default encodings used to guess which charset
-# an attachment uses if not specified. Must be recognized by
-# Encode::Guess.
+=item C<$StandaloneMinSpareServers>, C<$StandaloneMaxSpareServers>
-set( @EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii) );
+These next two options can be used to scale up and down the number of servers
+to adjust to load. These two options will respect the C<$StandaloneMinServers
+> and C<$StandaloneMaxServers options>.
+
+=cut
-# The charset for localized email. Must be recognized by Encode.
+Set($StandaloneMinSpareServers, 0);
+Set($StandaloneMaxSpareServers, 0);
-set( $EmailOutputEncoding, 'utf-8' );
+=item C<$StandaloneMaxRequests>
-# }}}
+This sets the absolute maximum number of requests a single server will serve.
+Setting this would be useful if, for example, memory usage slowly crawls up
+every hit.
-# {{{ RT date Handling Options
+=cut
+
+#Set($StandaloneMaxRequests, 50);
+
+=item C<%NetServerOptions>
+
+C<%NetServerOptions> is a hash of additional options to use for
+L<Net::Server/DEFAULT ARGUMENTS>. For example, you could set
+reverse_lookups to get the hostnames for all users with:
+
+C<Set(%NetServerOptions, (reverse_lookups => 1));>
+
+=cut
+
+Set(%NetServerOptions, ());
+
+=back
+
+
+=head1 UTF-8 Configuration
+
+=over 4
+
+=item C<@LexiconLanguages>
+
+An array that contains languages supported by RT's internationalization
+interface. Defaults to all *.po lexicons; setting it to C<qw(en ja)> will make
+RT bilingual instead of multilingual, but will save some memory.
+
+=cut
+
+Set(@LexiconLanguages, qw(*));
+
+=item C<@EmailInputEncodings>
+
+An array that contains default encodings used to guess which charset
+an attachment uses if not specified. Must be recognized by
+L<Encode::Guess>.
+
+=cut
+
+Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
+
+=item C<$EmailOutputEncoding>
+
+The charset for localized email. Must be recognized by Encode.
+
+=cut
+
+Set($EmailOutputEncoding, 'utf-8');
+
+
+=back
+
+=head1 Date Handling Configuration
+
+=over 4
+
+=item C<$DateTimeFormat>
+
+You can choose date and time format. See "Output formatters"
+section in perldoc F<lib/RT/Date.pm> for more options. This option can
+be overridden by users in their preferences.
+Some examples:
+
+C<Set($DateTimeFormat, { Format => 'ISO', Seconds => 0 });>
+C<Set($DateTimeFormat, 'RFC2822');>
+C<Set($DateTimeFormat, { Format => 'RFC2822', Seconds => 0, DayOfWeek => 0 });>
+
+=cut
-# You can choose date and time format. See "Output formatters"
-# section in perldoc lib/RT/Date.pm for more options. This option can
-# be overridden by users in their preferences.
-# Some examples:
-#set($date_time_format, { format => 'ISO', seconds => 0 });
-#set($date_time_format, 'RFC2822');
-#set($date_time_format, { format => 'RFC2822', seconds => 0, day_of_week => 0 });
-set( $date_time_format, 'default_format' );
+Set($DateTimeFormat, 'DefaultFormat');
# Next two options are for Time::ParseDate
-# set this to 1 if your local date convention looks like "dd/mm/yy"
-# instead of "mm/dd/yy".
-set( $date_day_before_month, 1 );
+=item C<$DateDayBeforeMonth>
-# Should "Tuesday" default to meaning "Next Tuesday" or "Last Tuesday"?
-# set to 0 for "Next" or 1 for "Last".
+Set this to 1 if your local date convention looks like "dd/mm/yy"
+instead of "mm/dd/yy".
-set( $AmbiguousDayInPast, 1 );
+=cut
+
+Set($DateDayBeforeMonth , 1);
+
+=item C<$AmbiguousDayInPast>, C<$AmbiguousDayInFuture>
+
+Should an unspecified day or year in a date refer to a future or a
+past value? For example, should a date of "Tuesday" default to mean
+the date for next Tuesday or last Tuesday? Should the date "March 1"
+default to the date for next March or last March?
+
+Set $<AmbiguousDayInPast> for the last date, or $<$AmbiguousDayInFuture> for the
+next date.
+
+The default is usually good.
+
+=cut
+
+Set($AmbiguousDayInPast, 0);
+Set($AmbiguousDayInFuture, 0);
+
+=back
+
+=head1 Miscellaneous Configuration
+
+=over 4
+
+=item C<@ActiveStatus>, C<@InactiveStatus>
+
+You can define new statuses and even reorder existing statuses here.
+WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
+will break horribly. The statuses you add must be no longer than
+10 characters.
+
+=cut
+
+Set(@ActiveStatus, qw(new open stalled));
+Set(@InactiveStatus, qw(resolved rejected deleted));
+
+=item C<$LinkTransactionsRun1Scrip>
+
+RT-3.4 backward compatibility setting. Add/Delete Link used to record one
+transaction and run one scrip. Set this value to 1 if you want
+only one of the link transactions to have scrips run.
-# }}}
+=cut
+
+Set($LinkTransactionsRun1Scrip, 0);
-# {{{ Miscellaneous RT settings
+=item C<$StrictLinkACL>
-# You can define new statuses and even reorder existing statuses here.
-# WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
-# will break horribly. The statuses you add must be no longer than
-# 10 characters.
+When this feature is enabled a user needs I<ModifyTicket> rights on both
+tickets to link them together, otherwise he can have rights on either of
+them.
-set( @ActiveStatus, qw(new open stalled) );
-set( @InactiveStatus, qw(resolved rejected deleted) );
+=cut
-# RT-3.4 backward compatibility setting. Add/Delete Link used to record one
-# transaction and run one scrip. set this value to 1 if you want
-# only one of the link transactions to have scrips run.
-set( $LinkTransactionsRun1Scrip, 0 );
+Set($StrictLinkACL, 1);
-# When this feature is enabled an user need ModifyTicket right on both
-# tickets to link them together, otherwise he can have right on any of
-# two.
-set( $StrictLinkACL, 1 );
+=item C<$PreviewScripMessages>
-# set $PreviewScripMessages to 1 if the scrips preview on the ticket
-# reply page should include the content of the messages to be sent.
+Set C<$PreviewScripMessages> to 1 if the scrips preview on the ticket
+reply page should include the content of the messages to be sent.
-# set $use_transaction_batch to 1 to execute transactions in batches,
-# such that a resolve and comment (for example) would happen
-# simultaneously, instead of as two transactions, unaware of each
-# others' existence.
+=cut
-# set @custom_field_valuesSources to a list of class names which extend
-# RT::Model::CustomFieldValueCollection::External. This can be used to pull lists of
-# custom field values from external sources at runtime.
+Set($PreviewScripMessages, 0);
-# }}}
+=item C<$UseTransactionBatch>
-# {{{ Development Mode
-#
-# RT comes with a "Development mode" setting.
-# This setting, as a convenience for developers, turns on
-# all sorts of development options that you most likely don't want in
-# production:
-#
-# * Turns off Mason's 'static_source' directive. By default, you can't
-# edit RT's web ui components on the fly and have RT magically pick up
-# your changes. (It's a big performance hit)
-#
-# * More to come
-#
+Set C<$UseTransactionBatch> to 1 to execute transactions in batches,
+such that a resolve and comment (for example) would happen
+simultaneously, instead of as two transactions, unaware of each
+others' existence.
+
+=cut
+
+Set($UseTransactionBatch, 0);
+
+=item C<@CustomFieldValuesSources>
+
+Set C<@CustomFieldValuesSources> to a list of class names which extend
+L<RT::CustomFieldValues::External>. This can be used to pull lists of
+custom field values from external sources at runtime.
+
+=cut
-set( $DevelMode, '0' );
+Set(@CustomFieldValuesSources, ());
-# }}}
+=item C<$CanonicalizeRedirectURLs>
-# {{{ Deprecated options
+Set C<$CanonicalizeRedirectURLs> to 1 to use $C<WebURL> when redirecting rather
+than the one we get from C<%ENV>.
-# $AlwaysUsebase64 - Encode blobs as base64 in DB (?)
-# $ticket_base_uri - base URI to tickets in this system; used when loading (?)
-# $UseCodeTickets - This option is exists for backwards compatibility. Don't use it.
+If you use RT behind a reverse proxy, you almost certainly want to
+enable this option.
-# }}}
+=cut
+
+Set($CanonicalizeRedirectURLs, 0);
+=item C<$EnableReminders>
+
+Hide links/portlets related to Reminders by setting this to 0
+
+=cut
+
+Set($EnableReminders,1);
+
+=back
+
+=head1 Development Configuration
+
+=over 4
+
+=item C<$DevelMode>
+
+RT comes with a "Development mode" setting.
+This setting, as a convenience for developers, turns on
+all sorts of development options that you most likely don't want in
+production:
+
+* Turns off Mason's 'static_source' directive. By default, you can't
+ edit RT's web ui components on the fly and have RT magically pick up
+ your changes. (It's a big performance hit)
+
+ * More to come
+
+=cut
+
+Set($DevelMode, '1');
+
+
+=back
+
+=head1 Deprecated Options
+
+=over 4
+
+=item C<$AlwaysUseBase64>
+
+Encode blobs as base64 in DB (?)
+
+=item C<$TicketBaseURI>
+
+Base URI to tickets in this system; used when loading (?)
+
+=item C<$UseCodeTickets>
+
+This option is exists for backwards compatibility. Don't use it.
+
+=back
+
+=cut
1;
More information about the Rt-commit
mailing list