Editing 0.11/TracIni

= The Trac Configuration File = ''[Note To Editors] Please discuss documentation changes in the [#Discussion] section. Even better, send us documentation patches against the ''code'' (i.e. where the configuration entries are documented), either on Trac-dev or on new tickets. '' [[TracGuideToc]] Trac configuration is done by editing the '''`trac.ini`''' config file, located in `<projectenv>/conf/trac.ini`. Changes to the configuration are usually reflected immediately, though changes to the `[components]` or `[logging]` sections will require restarting the web server. You may also need to restart the web server after creating a global configuration file when none was previously present. The `trac.ini` configuration file should be writable by the web server, as Trac currently relies on the possibility to trigger a complete environment reload to flush its caches. == Global Configuration == In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or /etc/trac/trac.ini, depending on the distribution. If you're upgrading, you may want to specify that file to inherit from. Literally, when you're upgrading to 0.11, you have to add an `[inherit]` section to your project's `trac.ini` file. Additionally, you have to move your customized templates and common images from `$prefix/share/trac/...` to the new location. Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows: {{{ [inherit] file = /usr/share/trac/conf/trac.ini }}} Note that you can also specify a global option file when creating a new project, by adding the option `--inherit=/path/to/global/options` to [TracAdmin trac-admin]'s `initenv` command. If do not do this but nevertheless intend to use a global option file with your new environment, you will have to go through the newly generated conf/trac.ini file and delete the entries that will otherwise override those set in the global file. == Reference == This is a brief reference of available configuration options. ''Note that the [bitten], [spam-filter] and [vote] sections below are added by plugins enabled on this Trac, and therefore won't be part of a default installation.'' {{{ #!comment Suggest your documentation fixes in the Discussion section at the bottom of the page, or better send us patches for the docstrings! }}} {{{#!html <div class="tracini"><h2 id="attachment-section">[attachment]</h2><table class="wiki"><tbody><tr><td><tt>max_size</tt></td><td>Maximum allowed file size (in bytes) for ticket and wiki attachments.</td></tr><tr><td><tt>render_unsafe_content</tt></td><td>Whether attachments should be rendered in the browser, or only made downloadable. Pretty much any file may be interpreted as HTML by the browser, which allows a malicious user to attach a file containing cross-site scripting attacks. For public sites where anonymous users can create attachments it is recommended to leave this option disabled (which is the default).</td></tr></tbody></table><h2 id="browser-section">[browser]</h2><table class="wiki"><tbody><tr><td><tt>color_scale</tt></td><td>Enable colorization of the <i>age</i> column. This uses the same color scale as the source code annotation: blue is older, red is newer. (<i>since 0.11</i>)</td></tr><tr><td><tt>downloadable_paths</tt></td><td>List of repository paths that can be downloaded. Leave the option empty if you want to disable all downloads, otherwise set it to a comma-separated list of authorized paths (those paths are glob patterns, i.e. "*" can be used as a wild card) (<i>since 0.10</i>)</td></tr><tr><td><tt>hide_properties</tt></td><td>Comma-separated list of version control properties to hide from the repository browser. (<i>since 0.9</i>)</td></tr><tr><td><tt>intermediate_color</tt></td><td>(r,g,b) color triple to use for the color corresponding to the intermediate color, if two linear interpolations are used for the color scale (see <tt>intermediate_point</tt>). If not set, the intermediate color between <tt>oldest_color</tt> and <tt>newest_color</tt> will be used. (<i>since 0.11</i>)</td></tr><tr><td><tt>intermediate_point</tt></td><td>If set to a value between 0 and 1 (exclusive), this will be the point chosen to set the <tt>intermediate_color</tt> for interpolating the color value. (<i>since 0.11</i>)</td></tr><tr><td><tt>newest_color</tt></td><td>(r,g,b) color triple to use for the color corresponding to the newest color, for the color scale used in <i>blame</i> or the browser <i>age</i> column if <tt>color_scale</tt> is enabled. (<i>since 0.11</i>)</td></tr><tr><td><tt>oldest_color</tt></td><td>(r,g,b) color triple to use for the color corresponding to the oldest color, for the color scale used in <i>blame</i> or the browser <i>age</i> column if <tt>color_scale</tt> is enabled. (<i>since 0.11</i>)</td></tr><tr><td><tt>oneliner_properties</tt></td><td>Comma-separated list of version control properties to render as oneliner wiki content in the repository browser. (<i>since 0.11</i>)</td></tr><tr><td><tt>render_unsafe_content</tt></td><td>Whether raw files should be rendered in the browser, or only made downloadable. Pretty much any file may be interpreted as HTML by the browser, which allows a malicious user to create a file containing cross-site scripting attacks. For open repositories where anyone can check-in a file, it is recommended to leave this option disabled (which is the default).</td></tr><tr><td><tt>wiki_properties</tt></td><td>Comma-separated list of version control properties to render as wiki content in the repository browser. (<i>since 0.11</i>)</td></tr></tbody></table><h2 id="changeset-section">[changeset]</h2><table class="wiki"><tbody><tr><td><tt>max_diff_bytes</tt></td><td>Maximum total size in bytes of the modified files (their old size plus their new size) for which the changeset view will attempt to show the diffs inlined (<i>since 0.10</i>).</td></tr><tr><td><tt>max_diff_files</tt></td><td>Maximum number of modified files for which the changeset view will attempt to show the diffs inlined (<i>since 0.10</i>).</td></tr><tr><td><tt>wiki_format_messages</tt></td><td>Whether wiki formatting should be applied to changeset messages. If this option is disabled, changeset messages will be rendered as pre-formatted text.</td></tr></tbody></table><h2 id="header_logo-section">[header_logo]</h2><table class="wiki"><tbody><tr><td><tt>alt</tt></td><td>Alternative text for the header logo.</td></tr><tr><td><tt>height</tt></td><td>Height of the header logo image in pixels.</td></tr><tr><td><tt>link</tt></td><td>URL to link to from header logo.</td></tr><tr><td><tt>src</tt></td><td>URL of the image to use as header logo.</td></tr><tr><td><tt>width</tt></td><td>Width of the header logo image in pixels.</td></tr></tbody></table><h2 id="inherit-section">[inherit]</h2><table class="wiki"><tbody><tr><td><tt>plugins_dir</tt></td><td>Path of the directory containing additional plugins. Plugins in that directory are loaded in addition to those in the directory of the environment <tt>plugins</tt>, with this one taking precedence. (<i>since 0.11</i>)</td></tr><tr><td><tt>templates_dir</tt></td><td>Path to the shared templates directory. Templates in that directory are loaded in addition to those in the environments <tt>templates</tt> directory, but the latter take precedence. (<i>since 0.11</i>)</td></tr></tbody></table><h2 id="logging-section">[logging]</h2><table class="wiki"><tbody><tr><td><tt>log_file</tt></td><td>If <tt>log_type</tt> is <tt>file</tt>, this should be a path to the log-file.</td></tr><tr><td><tt>log_format</tt></td><td>Custom logging format. If nothing is set, the following will be used: Trac[$(module)s] $(levelname)s: $(message)s In addition to regular key names supported by the Python logger library library (see <a class="ext-link" href="http://docs.python.org/lib/node422.html"><span class="icon"> </span>http://docs.python.org/lib/node422.html</a>), one could use: - $(path)s the path for the current environment - $(basename)s the last path component of the current environment - $(project)s the project name Note the usage of <tt>$(...)s</tt> instead of <tt>%(...)s</tt> as the latter form would be interpreted by the <a class="missing wiki" href="/wiki/ConfigParser" rel="nofollow">ConfigParser?</a> itself. Example: <tt>($(thread)d) Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s</tt> <i>(since 0.10.5)</i></td></tr><tr><td><tt>log_level</tt></td><td>Level of verbosity in log. Should be one of (<tt>CRITICAL</tt>, <tt>ERROR</tt>, <tt>WARN</tt>, <tt>INFO</tt>, <tt>DEBUG</tt>).</td></tr><tr><td><tt>log_type</tt></td><td>Logging facility to use. Should be one of (<tt>none</tt>, <tt>file</tt>, <tt>stderr</tt>, <tt>syslog</tt>, <tt>winlog</tt>).</td></tr></tbody></table><h2 id="milestone-section">[milestone]</h2><table class="wiki"><tbody><tr><td><tt>stats_provider</tt></td><td>Name of the component implementing <tt>ITicketGroupStatsProvider</tt>, which is used to collect statistics on groups of tickets for display in the milestone views.</td></tr></tbody></table><h2 id="mimeviewer-section">[mimeviewer]</h2><table class="wiki"><tbody><tr><td><tt>enscript_modes</tt></td><td>List of additional MIME types known by Enscript. For each, a tuple <tt>mimetype:mode:quality</tt> has to be specified, where <tt>mimetype</tt> is the MIME type, <tt>mode</tt> is the corresponding Enscript mode to be used for the conversion and <tt>quality</tt> is the quality ratio associated to this conversion. That can also be used to override the default quality ratio used by the Enscript render, which is 2 (<i>since 0.10</i>).</td></tr><tr><td><tt>enscript_path</tt></td><td>Path to the Enscript executable.</td></tr><tr><td><tt>max_preview_size</tt></td><td>Maximum file size for HTML preview. (<i>since 0.9</i>)</td></tr><tr><td><tt>mime_map</tt></td><td>List of additional MIME types and keyword mappings. Mappings are comma-separated, and for each MIME type, there's a colon (":") separated list of associated keywords or file extensions. (<i>since 0.10</i>)</td></tr><tr><td><tt>php_path</tt></td><td>Path to the PHP executable (<i>since 0.9</i>).</td></tr><tr><td><tt>pygments_default_style</tt></td><td>The default style to use for Pygments syntax highlighting.</td></tr><tr><td><tt>pygments_modes</tt></td><td>List of additional MIME types known by Pygments. For each, a tuple <tt>mimetype:mode:quality</tt> has to be specified, where <tt>mimetype</tt> is the MIME type, <tt>mode</tt> is the corresponding Pygments mode to be used for the conversion and <tt>quality</tt> is the quality ratio associated to this conversion. That can also be used to override the default quality ratio used by the Pygments render.</td></tr><tr><td><tt>tab_width</tt></td><td>Displayed tab width in file preview. (<i>since 0.9</i>)</td></tr><tr><td><tt>treat_as_binary</tt></td><td>Comma-separated list of MIME types that should be treated as binary data. (<i>since 0.11.5</i>)</td></tr></tbody></table><h2 id="notification-section">[notification]</h2><table class="wiki"><tbody><tr><td><tt>admit_domains</tt></td><td>Comma-separated list of domains that should be considered as valid for email addresses (such as localdomain)</td></tr><tr><td><tt>always_notify_owner</tt></td><td>Always send notifications to the ticket owner (<i>since 0.9</i>).</td></tr><tr><td><tt>always_notify_reporter</tt></td><td>Always send notifications to any address in the <i>reporter</i> field.</td></tr><tr><td><tt>always_notify_updater</tt></td><td>Always send notifications to the person who causes the ticket property change and to any previous updater of that ticket.</td></tr><tr><td><tt>ignore_domains</tt></td><td>Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains)</td></tr><tr><td><tt>mime_encoding</tt></td><td>Specifies the MIME encoding scheme for emails. Valid options are 'base64' for Base64 encoding, 'qp' for Quoted-Printable, and 'none' for no encoding, in which case mails will be sent as 7bit if the content is all ASCII, or 8bit otherwise. (<i>since 0.10</i>)</td></tr><tr><td><tt>notify_on_failed_build</tt></td><td>Notify if bitten build fails.</td></tr><tr><td><tt>notify_on_successful_build</tt></td><td>Notify if bitten build succeeds.</td></tr><tr><td><tt>smtp_always_bcc</tt></td><td>Email address(es) to always send notifications to, addresses do not appear publicly (Bcc:). (<i>since 0.10</i>).</td></tr><tr><td><tt>smtp_always_cc</tt></td><td>Email address(es) to always send notifications to, addresses can be seen by all recipients (Cc:).</td></tr><tr><td><tt>smtp_default_domain</tt></td><td>Default host/domain to append to address that do not specify one</td></tr><tr><td><tt>smtp_enabled</tt></td><td>Enable SMTP (email) notification.</td></tr><tr><td><tt>smtp_from</tt></td><td>Sender address to use in notification emails.</td></tr><tr><td><tt>smtp_from_name</tt></td><td>Sender name to use in notification emails.</td></tr><tr><td><tt>smtp_password</tt></td><td>Password for SMTP server. (<i>since 0.9</i>).</td></tr><tr><td><tt>smtp_port</tt></td><td>SMTP server port to use for email notification.</td></tr><tr><td><tt>smtp_replyto</tt></td><td>Reply-To address to use in notification emails.</td></tr><tr><td><tt>smtp_server</tt></td><td>SMTP server hostname to use for email notifications.</td></tr><tr><td><tt>smtp_subject_prefix</tt></td><td>Text to prepend to subject line of notification emails. If the setting is not defined, then the [$project_name] prefix. If no prefix is desired, then specifying an empty option will disable it. (<i>since 0.10.1</i>).</td></tr><tr><td><tt>smtp_user</tt></td><td>Username for SMTP server. (<i>since 0.9</i>).</td></tr><tr><td><tt>ticket_subject_template</tt></td><td>A Genshi text template snippet used to get the notification subject. By default, the subject template is <tt>$prefix #$ticket.id: $summary</tt>. <tt>$prefix</tt> being the value of the <tt>smtp_subject_prefix</tt> option. <i>(since 0.11)</i></td></tr><tr><td><tt>use_public_cc</tt></td><td>Recipients can see email addresses of other CC'ed recipients. If this option is disabled (the default), recipients are put on BCC (<i>since 0.10</i>).</td></tr><tr><td><tt>use_short_addr</tt></td><td>Permit email address without a host/domain (i.e. username only) The SMTP server should accept those addresses, and either append a FQDN or use local delivery (<i>since 0.10</i>).</td></tr><tr><td><tt>use_tls</tt></td><td>Use SSL/TLS to send notifications (<i>since 0.10</i>).</td></tr></tbody></table><h2 id="project-section">[project]</h2><table class="wiki"><tbody><tr><td><tt>admin</tt></td><td>E-Mail address of the project's administrator.</td></tr><tr><td><tt>admin_trac_url</tt></td><td>Base URL of a Trac instance where errors in this Trac should be reported. This can be an absolute or relative URL, or '.' to reference this Trac instance. An empty value will disable the reporting buttons. (<i>since 0.11.3</i>)</td></tr><tr><td><tt>descr</tt></td><td>Short description of the project.</td></tr><tr><td><tt>footer</tt></td><td>Page footer text (right-aligned).</td></tr><tr><td><tt>icon</tt></td><td>URL of the icon of the project.</td></tr><tr><td><tt>name</tt></td><td>Name of the project.</td></tr><tr><td><tt>url</tt></td><td>URL of the main project web site, usually the website in which the <tt>base_url</tt> resides.</td></tr></tbody></table><h2 id="query-section">[query]</h2><table class="wiki"><tbody><tr><td><tt>default_anonymous_query</tt></td><td>The default query for anonymous users. The query is either in <a class="wiki" href="/wiki/TracQuery#QueryLanguage">query language</a> syntax, or a URL query string starting with <tt>?</tt> as used in <tt>query:</tt> <a class="wiki" href="/wiki/TracQuery#UsingTracLinks">Trac links</a>. (<i>since 0.11.2</i>)</td></tr><tr><td><tt>default_query</tt></td><td>The default query for authenticated users. The query is either in <a class="wiki" href="/wiki/TracQuery#QueryLanguage">query language</a> syntax, or a URL query string starting with <tt>?</tt> as used in <tt>query:</tt> <a class="wiki" href="/wiki/TracQuery#UsingTracLinks">Trac links</a>. (<i>since 0.11.2</i>)</td></tr><tr><td><tt>items_per_page</tt></td><td>Number of tickets displayed per page in ticket queries, by default (<i>since 0.11</i>)</td></tr></tbody></table><h2 id="report-section">[report]</h2><table class="wiki"><tbody><tr><td><tt>items_per_page</tt></td><td>Number of tickets displayed per page in ticket reports, by default (<i>since 0.11</i>)</td></tr><tr><td><tt>items_per_page_rss</tt></td><td>Number of tickets displayed in the rss feeds for reports (<i>since 0.11</i>)</td></tr></tbody></table><h2 id="revisionlog-section">[revisionlog]</h2><table class="wiki"><tbody><tr><td><tt>default_log_limit</tt></td><td>Default value for the limit argument in the <a class="wiki" href="/wiki/TracRevisionLog">TracRevisionLog</a> (<i>since 0.11</i>).</td></tr></tbody></table><h2 id="roadmap-section">[roadmap]</h2><table class="wiki"><tbody><tr><td><tt>stats_provider</tt></td><td>Name of the component implementing <tt>ITicketGroupStatsProvider</tt>, which is used to collect statistics on groups of tickets for display in the roadmap views.</td></tr></tbody></table><h2 id="search-section">[search]</h2><table class="wiki"><tbody><tr><td><tt>min_query_length</tt></td><td>Minimum length of query string allowed when performing a search.</td></tr></tbody></table><h2 id="svn-section">[svn]</h2><table class="wiki"><tbody><tr><td><tt>branches</tt></td><td>Comma separated list of paths categorized as branches. If a path ends with '*', then all the directory entries found below that path will be included. Example: <tt>/trunk, /branches/*, /projectAlpha/trunk, /sandbox/*</tt></td></tr><tr><td><tt>tags</tt></td><td>Comma separated list of paths categorized as tags. If a path ends with '*', then all the directory entries found below that path will be included. Example: <tt>/tags/*, /projectAlpha/tags/A-1.0, /projectAlpha/tags/A-v1.1</tt></td></tr></tbody></table><h2 id="ticket-section">[ticket]</h2><table class="wiki"><tbody><tr><td><tt>default_cc</tt></td><td>Default cc: list for newly created tickets.</td></tr><tr><td><tt>default_component</tt></td><td>Default component for newly created tickets.</td></tr><tr><td><tt>default_description</tt></td><td>Default description for newly created tickets.</td></tr><tr><td><tt>default_keywords</tt></td><td>Default keywords for newly created tickets.</td></tr><tr><td><tt>default_milestone</tt></td><td>Default milestone for newly created tickets.</td></tr><tr><td><tt>default_owner</tt></td><td>Default owner for newly created tickets.</td></tr><tr><td><tt>default_priority</tt></td><td>Default priority for newly created tickets.</td></tr><tr><td><tt>default_resolution</tt></td><td>Default resolution for resolving (closing) tickets (<i>since 0.11</i>).</td></tr><tr><td><tt>default_severity</tt></td><td>Default severity for newly created tickets.</td></tr><tr><td><tt>default_summary</tt></td><td>Default summary (title) for newly created tickets.</td></tr><tr><td><tt>default_type</tt></td><td>Default type for newly created tickets (<i>since 0.9</i>).</td></tr><tr><td><tt>default_version</tt></td><td>Default version for newly created tickets.</td></tr><tr><td><tt>max_comment_size</tt></td><td>Don't accept tickets with a too big comment. (<i>since 0.11.2</i>)</td></tr><tr><td><tt>max_description_size</tt></td><td>Don't accept tickets with a too big description. (<i>since 0.11</i>).</td></tr><tr><td><tt>preserve_newlines</tt></td><td>Whether Wiki formatter should respect the new lines present in the Wiki text. If set to 'default', this is equivalent to 'yes' for new environments but keeps the old behavior for upgraded environments (i.e. 'no'). (<i>since 0.11</i>).</td></tr><tr><td><tt>restrict_owner</tt></td><td>Make the owner field of tickets use a drop-down menu. Be sure to understand the performance implications before activating this option. See <a class="wiki" href="/wiki/TracTickets#Assign-toasDrop-DownList">Assign-to as Drop-Down List</a> (<i>since 0.9</i>).</td></tr><tr><td><tt>workflow</tt></td><td>Ordered list of workflow controllers to use for ticket actions (<i>since 0.11</i>).</td></tr></tbody></table><h2 id="timeline-section">[timeline]</h2><table class="wiki"><tbody><tr><td><tt>abbreviated_messages</tt></td><td>Whether wiki-formatted event messages should be truncated or not. This only affects the default rendering, and can be overriden by specific event providers, see their own documentation. (<i>Since 0.11</i>)</td></tr><tr><td><tt>changeset_collapse_events</tt></td><td>Whether consecutive changesets from the same author having exactly the same message should be presented as one event. That event will link to the range of changesets in the log view. (<i>since 0.11</i>)</td></tr><tr><td><tt>changeset_long_messages</tt></td><td>Whether wiki-formatted changeset messages should be multiline or not. If this option is not specified or is false and <tt>wiki_format_messages</tt> is set to true, changeset messages will be single line only, losing some formatting (bullet points, etc).</td></tr><tr><td><tt>changeset_show_files</tt></td><td>Number of files to show (<tt>-1</tt> for unlimited, <tt>0</tt> to disable). This can also be <tt>location</tt>, for showing the common prefix for the changed files. (since 0.11).</td></tr><tr><td><tt>default_daysback</tt></td><td>Default number of days displayed in the Timeline, in days. (<i>since 0.9.</i>)</td></tr><tr><td><tt>max_daysback</tt></td><td>Maximum number of days (-1 for unlimited) displayable in the Timeline. (<i>since 0.11</i>)</td></tr><tr><td><tt>newticket_formatter</tt></td><td>Which formatter flavor (e.g. 'html' or 'oneliner') should be used when presenting the description for new tickets. If 'oneliner', the [timeline] abbreviated_messages option applies. (<i>since 0.11</i>).</td></tr><tr><td><tt>ticket_show_details</tt></td><td>Enable the display of all ticket changes in the timeline, not only open / close operations (<i>since 0.9</i>).</td></tr></tbody></table><h2 id="trac-section">[trac]</h2><table class="wiki"><tbody><tr><td><tt>authz_file</tt></td><td>Path to Subversion <a class="ext-link" href="http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.2"><span class="icon"> </span>authorization (authz) file</a></td></tr><tr><td><tt>authz_module_name</tt></td><td>The module prefix used in the authz_file.</td></tr><tr><td><tt>auto_reload</tt></td><td>Automatically reload template files after modification.</td></tr><tr><td><tt>backup_dir</tt></td><td>Database backup location</td></tr><tr><td><tt>base_url</tt></td><td>Reference URL for the Trac deployment. This is the base URL that will be used when producing documents that will be used outside of the web browsing context, like for example when inserting URLs pointing to Trac resources in notification e-mails.</td></tr><tr><td><tt>check_auth_ip</tt></td><td>Whether the IP address of the user should be checked for authentication (<i>since 0.9</i>).</td></tr><tr><td><tt>database</tt></td><td>Database connection <a class="wiki" href="/wiki/TracEnvironment#DatabaseConnectionStrings">string</a> for this project</td></tr><tr><td><tt>debug_sql</tt></td><td>Show the SQL queries in the Trac log, at DEBUG level. <i>(Since 0.11.5)</i></td></tr><tr><td><tt>default_charset</tt></td><td>Charset to be used when in doubt.</td></tr><tr><td><tt>default_handler</tt></td><td>Name of the component that handles requests to the base URL. Options include <tt>TimelineModule</tt>, <tt>RoadmapModule</tt>, <tt>BrowserModule</tt>, <tt>QueryModule</tt>, <tt>ReportModule</tt>, <tt>TicketModule</tt> and <tt>WikiModule</tt>. The default is <tt>WikiModule</tt>. (<i>since 0.9</i>)</td></tr><tr><td><tt>default_timezone</tt></td><td>The default timezone to use</td></tr><tr><td><tt>htdocs_location</tt></td><td>Base URL of the core static resources.</td></tr><tr><td><tt>ignore_auth_case</tt></td><td>Whether login names should be converted to lower case (<i>since 0.9</i>).</td></tr><tr><td><tt>mainnav</tt></td><td>Order of the items to display in the <tt>mainnav</tt> navigation bar, listed by IDs. See also <a class="missing wiki" href="/wiki/TracNavigation" rel="nofollow">TracNavigation?</a>.</td></tr><tr><td><tt>metanav</tt></td><td>Order of the items to display in the <tt>metanav</tt> navigation bar, listed by IDs. See also <a class="missing wiki" href="/wiki/TracNavigation" rel="nofollow">TracNavigation?</a>.</td></tr><tr><td><tt>mysqldump_path</tt></td><td>Location of mysqldump for MySQL database backups</td></tr><tr><td><tt>never_obfuscate_mailto</tt></td><td>Never obfuscate <tt>mailto:</tt> links explicitly written in the wiki, even if <tt>show_email_addresses</tt> is false or the user has not the EMAIL_VIEW permission (<i>since 0.11.6</i>).</td></tr><tr><td><tt>permission_policies</tt></td><td>List of components implementing <tt>IPermissionPolicy</tt>, in the order in which they will be applied. These components manage fine-grained access control to Trac resources. Defaults to the <a class="missing wiki" href="/wiki/DefaultPermissionPolicy" rel="nofollow">DefaultPermissionPolicy?</a> (pre-0.11 behavior) and <a class="missing wiki" href="/wiki/LegacyAttachmentPolicy" rel="nofollow">LegacyAttachmentPolicy?</a> (map ATTACHMENT_* permissions to realm specific ones)</td></tr><tr><td><tt>permission_store</tt></td><td>Name of the component implementing <tt>IPermissionStore</tt>, which is used for managing user and group permissions.</td></tr><tr><td><tt>pg_dump_path</tt></td><td>Location of pg_dump for Postgres database backups</td></tr><tr><td><tt>repository_dir</tt></td><td>Path to local repository. This can also be a relative path (<i>since 0.11</i>).</td></tr><tr><td><tt>repository_type</tt></td><td>Repository connector type. (<i>since 0.10</i>)</td></tr><tr><td><tt>request_filters</tt></td><td>Ordered list of filters to apply to all requests (<i>since 0.10</i>).</td></tr><tr><td><tt>secure_cookies</tt></td><td>Restrict cookies to HTTPS connections. When true, set the <tt>secure</tt> flag on all cookies so that they are only sent to the server on HTTPS connections. Use this if your Trac instance is only accessible through HTTPS. (<i>since 0.11.2</i>)</td></tr><tr><td><tt>show_email_addresses</tt></td><td>Show email addresses instead of usernames. If false, we obfuscate email addresses (<i>since 0.11</i>).</td></tr><tr><td><tt>show_ip_addresses</tt></td><td>Show IP addresses for resource edits (e.g. wiki). (<i>since 0.11.3</i>).</td></tr><tr><td><tt>timeout</tt></td><td>Timeout value for database connection, in seconds. Use '0' to specify <i>no timeout</i>. <i>(Since 0.11)</i></td></tr><tr><td><tt>use_base_url_for_redirect</tt></td><td>Optionally use <tt>[trac] base_url</tt> for redirects. In some configurations, usually involving running Trac behind a HTTP proxy, Trac can't automatically reconstruct the URL that is used to access it. You may need to use this option to force Trac to use the <tt>base_url</tt> setting also for redirects. This introduces the obvious limitation that this environment will only be usable when accessible from that URL, as redirects are frequently used. <i>(since 0.10.5)</i></td></tr></tbody></table><h2 id="wiki-section">[wiki]</h2><table class="wiki"><tbody><tr><td><tt>ignore_missing_pages</tt></td><td>Enable/disable highlighting <a class="wiki" href="/wiki/CamelCase">CamelCase</a> links to missing pages (<i>since 0.9</i>).</td></tr><tr><td><tt>max_size</tt></td><td>Maximum allowed wiki page size in bytes. (<i>since 0.11.2</i>)</td></tr><tr><td><tt>render_unsafe_content</tt></td><td>Enable/disable the use of unsafe HTML tags such as <tt>&lt;script&gt;</tt> or <tt>&lt;embed&gt;</tt> with the HTML <a class="wiki" href="/wiki/WikiProcessors">WikiProcessor</a> (<i>since 0.10.4</i>). For public sites where anonymous users can edit the wiki it is recommended to leave this option disabled (which is the default).</td></tr><tr><td><tt>split_page_names</tt></td><td>Enable/disable splitting the <a class="wiki" href="/wiki/WikiPageNames">WikiPageNames</a> with space characters (<i>since 0.10</i>).</td></tr></tbody></table></div> }}} === [components] === #components-section This section is used to enable or disable components provided by plugins, as well as by Trac itself. The component to enable/disable is specified via the name of the option. Whether its enabled is determined by the option value; setting the value to `enabled` or `on` will enable the component, any other value (typically `disabled` or `off`) will disable the component. The option name is either the fully qualified name of the components or the module/package prefix of the component. The former enables/disables a specific component, while the latter enables/disables any component in the specified package/module. Consider the following configuration snippet: {{{ [components] trac.ticket.report.ReportModule = disabled webadmin.* = enabled }}} The first option tells Trac to disable the [wiki:TracReports report module]. The second option instructs Trac to enable all components in the `webadmin` package. Note that the trailing wildcard is required for module/package matching. See the ''Plugins'' page on ''About Trac'' to get the list of active components (requires `CONFIG_VIEW` [wiki:TracPermissions permissions].) See also: TracPlugins === [ticket-custom] === #ticket-custom-section In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details. === [ticket-workflow] === #ticket-workflow-section ''(since 0.11)'' The workflow for tickets is controlled by plugins. By default, there's only a `ConfigurableTicketWorkflow` component in charge. That component allows the workflow to be configured via this section in the trac.ini file. See TracWorkflow for more details. === [milestone-groups] === #milestone-groups-section ''(since 0.11)'' As the workflow for tickets is now configurable, there can be many ticket states, and simply displaying closed tickets vs. all the others is maybe not appropriate in all cases. This section enables one to easily create ''groups'' of states that will be shown in different colors in the milestone progress bar. Example configuration (the default only has closed and active): {{{ closed = closed # sequence number in the progress bar closed.order = 0 # optional extra param for the query (two additional columns: created and modified and sort on created) closed.query_args = group=resolution,order=time,col=id,col=summary,col=owner,col=type,col=priority,col=component,col=severity,col=time,col=changetime # indicates groups that count for overall completion closed.overall_completion = truepercentage new = new new.order = 1 new.css_class = new new.label = new # one catch-all group is allowed active = * active.order = 2 # CSS class for this interval active.css_class = open # Displayed label for this group active.label = in progress }}} The definition consists in a comma-separated list of accepted status. Also, '*' means any status and could be used to associate all remaining states to one catch-all group. The CSS class can be one of: new (yellow), open (no color) or closed (green). New styles can easily be added using the following selector: `table.progress td.<class>` === [svn:externals] === #svn:externals-section ''(since 0.11)'' The TracBrowser for Subversion can interpret the `svn:externals` property of folders. By default, it only turns the URLs into links as Trac can't browse remote repositories. However, if you have another Trac instance (or an other repository browser like [http://www.viewvc.org/ ViewVC]) configured to browse the target repository, then you can instruct Trac which other repository browser to use for which external URL. This mapping is done in the `[svn:externals]` section of the TracIni Example: {{{ [svn:externals] 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev 3 = http://theirserver.org/svn/eng-soft http://ourserver/viewvc/svn/$path/?pathrev=25914 4 = svn://anotherserver.com/tools_repository http://ourserver/tracs/tools/browser/$path?rev=$rev }}} With the above, the `svn://anotherserver.com/tools_repository/tags/1.1/tools` external will be mapped to `http://ourserver/tracs/tools/browser/tags/1.1/tools?rev=` (and `rev` will be set to the appropriate revision number if the external additionally specifies a revision, see the [http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html SVN Book on externals] for more details). Note that the number used as a key in the above section is purely used as a place holder, as the URLs themselves can't be used as a key due to various limitations in the configuration file parser. Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. == Discussion == ''Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.'' * There is, apparently, an [svn] `repository_url` option that is not documented here. [[br]] No, there's no such thing. There ''might'' be a plugin providing support for this, for Trac 0.12. However, Trac 0.12 will support an `url` property for repositories. * It can be helpful to know the default values for each entry, perhaps specified in a common format such as square brackets [] at the end of the description (or at the beginning of the description). ''for 0.12?'' * Due to TracIni macros, there is no history of trac.ini settings changes between versions, and sometimes it is worthy to know when some some setting was removed. ---- See also: TracGuide, TracAdmin, TracEnvironment