= The Trac Configuration File =
[[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.

== Global Configuration ==

==== Trac 0.9 and 0.10 ====
Since version 0.9, Trac can also read the configuration from a global `trac.ini` file. These global options will then be merged with the environment-specific options, where local options override global options.

The global configuration is by default located in `$prefix/share/trac/conf/trac.ini`. It can be moved to a different location (for example, `/etc/trac.ini`), but that requires changing the file `trac/siteconfig.py` which gets created when Trac is installed.

==== Trac 0.11 ====
Since version 0.11 you must explicitly note which file to inherit from:
{{{
[inherit]
file = /usr/share/trac/conf/trac.ini
}}}

== Reference ==

This is a brief reference of available configuration options.

[[TracIni]]

== [components] ==
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] ==

In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.

== [svn:externals] ==
''(since 0.11)''

The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box.
However, if those externals are ''not'' using the `http:` protocol, or if a link to a different repository browser (such another Trac or [http://www.viewvc.org/ ViewVC]) is desired, then Trac needs to be able to map an external prefix to this other URL.

This mapping is done in the `[svn:externals]` section of the TracIni

Example:
{{{
[svn:externals]
http://theirserver.org/svn/eng-soft       http://ourserver/viewvc/svn/$path/?pathrev=25914
svn://anotherserver.com/tools_repository  http://ourserver/trac/support/browser/$path?rev=$rev
}}}
With the above, the `svn://anotherserver.com/tools_repository/tags/1.1/tools` external will be mapped to `http://ourserver/trac/support/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).


----
See also: TracGuide, TracAdmin, TracEnvironment