Legend:

Trac configuration is done by editing the '''`trac.ini`''' config file, located in `<projectenv>/conf/trac.ini`.

5

4

6

5

== Global Configuration ==

7

6

8

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.

7

In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or sometimes /etc/trac/trac.ini depending on the distribution. If you're upgrading, you may want to specify that file to inherit from.

9

8

10

The global configuration is by default localted 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.

9

Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:

10

{{{

11

[inherit]

12

file = /usr/share/trac/conf/trac.ini

13

}}}

14

15

Note that you can also specify a global option file when creating a new project, by adding the option

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.

''Note that prior to Trac r2335 (that applies to 0.9b1 and 0.9b2), you would use a `[disabled_components]` section instead. See a [http://projects.edgewall.com/trac/wiki/TracIni?version=42 previous version] of this page for the details.''

47

== [ticket-custom] == #ticket-custom-section

48

49

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

50

51

== [ticket-workflow] == #ticket-workflow-section

52

''(since 0.11)''

53

54

The workflow for tickets is controlled by plugins.

55

By default, there's only a `ConfigurableTicketWorkflow` component in charge.

56

That component allows the workflow to be configured via this section in the trac.ini file.

57

See TracWorkflow for more details.

58

59

== [milestone-groups] == #milestone-groups-section

60

''(since 0.11)''

61

62

As the workflow for tickets is now configurable, there can be many ticket states,

63

and simply displaying closed tickets vs. all the others is maybe not appropriate

64

in all cases. This section enables one to easily create ''groups'' of states

Also, '*' means any status and could be used to associate all remaining

82

states to one catch-all group.

83

84

The CSS class can be one of: new (yellow), open (no color) or

85

closed (green). New styles can easily be added using the following

86

selector: `table.progress td.<class>`

87

88

== [svn:externals] == #svn:externals-section

89

''(since 0.11)''

90

91

The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box.

92

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.

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).

105

106

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.