Changes between Version 2 and Version 3 of TracIni
- Timestamp:
- May 6, 2010, 11:40:33 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracIni
v2 v3 19 19 20 20 21 == Reference ==21 == Reference for settings 22 22 23 23 This is a brief reference of available configuration options. 24 24 25 ''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.'' 25 [[TracIni]] 26 26 27 [[TracIni()]] 27 == Reference for special sections 28 [[PageOutline(3,,inline)]] 28 29 29 30 == [components] == #components-section 30 === [components] === #components-section 31 31 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. 32 32 … … 46 46 See also: TracPlugins 47 47 48 == [ticket-custom] == #ticket-custom-section 49 50 In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details. 51 52 == [ticket-workflow] == #ticket-workflow-section 53 ''(since 0.11)'' 54 55 The workflow for tickets is controlled by plugins. 56 By default, there's only a `ConfigurableTicketWorkflow` component in charge. 57 That component allows the workflow to be configured via this section in the trac.ini file. 58 See TracWorkflow for more details. 59 60 == [milestone-groups] == #milestone-groups-section 48 === [milestone-groups] === #milestone-groups-section 61 49 ''(since 0.11)'' 62 50 … … 72 60 closed.order = 0 73 61 # optional extra param for the query (two additional columns: created and modified and sort on created) 74 group=resolution,order=time,col=id,col=summary,col=owner,col=type,col=priority,col=component,col=severity,col=time,col=changetime62 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 75 63 # indicates groups that count for overall completion 76 64 closed.overall_completion = truepercentage … … 98 86 selector: `table.progress td.<class>` 99 87 100 == [svn:externals] == #svn:externals-section 88 === [repositories] === #repositories-section 89 90 (''since 0.12'' multirepos) 91 92 One of the alternatives for registering new repositories is to populate the `[repositories]` section of the trac.ini. 93 94 This is especially suited for setting up convenience aliases, short-lived repositories, or during the initial phases of an installation. 95 96 See [TracRepositoryAdmin#Intrac.ini TracRepositoryAdmin] for details about the format adopted for this section and the rest of that page for the other alternatives. 97 98 === [svn:externals] === #svn:externals-section 101 99 ''(since 0.11)'' 102 100 103 The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box. 104 However, if those externals are ''not'' using the `http:` or `https:` protocol, or if a link to a different repository browser such as 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. 101 The TracBrowser for Subversion can interpret the `svn:externals` property of folders. 102 By default, it only turns the URLs into links as Trac can't browse remote repositories. 103 104 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. 105 105 106 106 This mapping is done in the `[svn:externals]` section of the TracIni … … 109 109 {{{ 110 110 [svn:externals] 111 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev112 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev111 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev 112 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev 113 113 3 = http://theirserver.org/svn/eng-soft http://ourserver/viewvc/svn/$path/?pathrev=25914 114 114 4 = svn://anotherserver.com/tools_repository http://ourserver/tracs/tools/browser/$path?rev=$rev … … 120 120 Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. 121 121 122 === [ticket-custom] === #ticket-custom-section 123 124 In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details. 125 126 === [ticket-workflow] === #ticket-workflow-section 127 ''(since 0.11)'' 128 129 The workflow for tickets is controlled by plugins. 130 By default, there's only a `ConfigurableTicketWorkflow` component in charge. 131 That component allows the workflow to be configured via this section in the trac.ini file. 132 See TracWorkflow for more details. 133 134 122 135 ---- 123 136 See also: TracGuide, TracAdmin, TracEnvironment