![(please configure the [header_logo] section in trac.ini)](/projects/oscar/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 1 and Version 2 of TracIni
- Timestamp:
- Oct 23, 2010, 8:43:57 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracIni
v1 v2 1 1 = The Trac Configuration File = 2 [[TracGuideToc]] 2 3 3 [[TracGuideToc]] 4 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. 5 6 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. 4 7 5 8 == Global Configuration == 6 9 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.10 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. 8 11 9 12 Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows: 10 13 {{{ 11 14 [inherit] 12 file = / usr/share/trac/conf/trac.ini15 file = /path/to/global/trac.ini 13 16 }}} 17 Multiple files can be specified using a comma-separated list. 14 18 15 Note that you can also specify a global option file when creating a new project, by adding the option 16 `--inherit=/path/to/global/options` to [TracAdmin trac-admin]'s `initenv` command. 17 If you would not do this but nevertheless intend to use a global option file with your new environment, 18 you would have to go through the newly generated conf/trac.ini file and delete the entries that would 19 otherwise override those set in the global file. 19 Note that you can also specify a global option file when creating a new project, by adding the option `--inherit=/path/to/global/trac.ini` to [TracAdmin#initenv trac-admin]'s `initenv` command. If you 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. 20 20 21 There are two more entries in the [[#inherit-section| [inherit] ]] section, `templates_dir` for sharing global templates and `plugins_dir`, for sharing plugins. Those entries can themselves be specified in the shared configuration file, and in fact, configuration files can even be chained if you specify another `[inherit] file` there. 21 22 22 == Reference ==23 == Reference for settings 23 24 24 25 This is a brief reference of available configuration options. 25 26 26 [[TracIni ()]]27 [[TracIni]] 27 28 29 == Reference for special sections 30 [[PageOutline(3,,inline)]] 28 31 29 == [components]== #components-section32 === [components] === #components-section 30 33 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. 31 34 … … 45 48 See also: TracPlugins 46 49 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 50 === [milestone-groups] === #milestone-groups-section 60 51 ''(since 0.11)'' 61 52 … … 65 56 that will be shown in different colors in the milestone progress bar. 66 57 67 Example configuration ( which is also the default):58 Example configuration (the default only has closed and active): 68 59 {{{ 69 60 closed = closed 70 closed.order = 0 # sequence number in the progress bar 71 closed.query_args = group=resolution # optional extra param for the query 72 closed.overall_completion = true # count for overall completion 61 # sequence number in the progress bar 62 closed.order = 0 63 # optional extra param for the query (two additional columns: created and modified and sort on created) 64 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 65 # indicates groups that count for overall completion 66 closed.overall_completion = truepercentage 73 67 74 active = * # one catch-all group is allowed 75 active.order = 1 76 active.css_class = open # CSS class for this interval 77 active.label = in progress # Displayed label for this group 68 new = new 69 new.order = 1 70 new.css_class = new 71 new.label = new 72 73 # one catch-all group is allowed 74 active = * 75 active.order = 2 76 # CSS class for this interval 77 active.css_class = open 78 # Displayed label for this group 79 active.label = in progress 78 80 }}} 79 81 … … 86 88 selector: `table.progress td.<class>` 87 89 88 == [svn:externals] == #svn:externals-section 90 === [repositories] === #repositories-section 91 92 (''since 0.12'' multirepos) 93 94 One of the alternatives for registering new repositories is to populate the `[repositories]` section of the trac.ini. 95 96 This is especially suited for setting up convenience aliases, short-lived repositories, or during the initial phases of an installation. 97 98 See [TracRepositoryAdmin#Intrac.ini TracRepositoryAdmin] for details about the format adopted for this section and the rest of that page for the other alternatives. 99 100 === [svn:externals] === #svn:externals-section 89 101 ''(since 0.11)'' 90 102 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. 103 The TracBrowser for Subversion can interpret the `svn:externals` property of folders. 104 By default, it only turns the URLs into links as Trac can't browse remote repositories. 105 106 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. 93 107 94 108 This mapping is done in the `[svn:externals]` section of the TracIni … … 97 111 {{{ 98 112 [svn:externals] 99 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev100 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev113 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev 114 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev 101 115 3 = http://theirserver.org/svn/eng-soft http://ourserver/viewvc/svn/$path/?pathrev=25914 102 4 = svn://anotherserver.com/tools_repository http://ourserver/trac /support/browser/$path?rev=$rev116 4 = svn://anotherserver.com/tools_repository http://ourserver/tracs/tools/browser/$path?rev=$rev 103 117 }}} 104 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).118 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). 105 119 106 120 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. 107 121 122 Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. 123 124 === [ticket-custom] === #ticket-custom-section 125 126 In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details. 127 128 === [ticket-workflow] === #ticket-workflow-section 129 ''(since 0.11)'' 130 131 The workflow for tickets is controlled by plugins. 132 By default, there's only a `ConfigurableTicketWorkflow` component in charge. 133 That component allows the workflow to be configured via this section in the trac.ini file. 134 See TracWorkflow for more details. 135 136 108 137 ---- 109 138 See also: TracGuide, TracAdmin, TracEnvironment
