Changes between Version 1 and Version 2 of TracIni
- Время:
- 21 июн. 2010 г., 16:31:21 (16 лет назад)
Обозначения:
- Без изменений
- Добавлено
- Удалено
- Изменено
-
TracIni
v1 v2 13 13 {{{ 14 14 [inherit] 15 file = / path/to/global/trac.ini15 file = /usr/share/trac/conf/trac.ini 16 16 }}} 17 Multiple files can be specified using a comma-separated list.18 17 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.18 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. 20 19 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.22 20 23 == Reference for settings21 == Reference == 24 22 25 23 This is a brief reference of available configuration options. 26 24 27 [[TracIni]] 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.'' 28 26 29 == Reference for special sections 30 [[PageOutline(3,,inline)]] 27 [[TracIni()]] 31 28 32 === [components] === #components-section 29 30 == [components] == #components-section 33 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. 34 32 … … 48 46 See also: TracPlugins 49 47 50 === [milestone-groups] === #milestone-groups-section 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 51 61 ''(since 0.11)'' 52 62 … … 62 72 closed.order = 0 63 73 # 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=changetime74 group=resolution,order=time,col=id,col=summary,col=owner,col=type,col=priority,col=component,col=severity,col=time,col=changetime 65 75 # indicates groups that count for overall completion 66 76 closed.overall_completion = truepercentage … … 88 98 selector: `table.progress td.<class>` 89 99 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 100 == [svn:externals] == #svn:externals-section 101 101 ''(since 0.11)'' 102 102 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. 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. 107 105 108 106 This mapping is done in the `[svn:externals]` section of the TracIni … … 111 109 {{{ 112 110 [svn:externals] 113 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev114 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 115 113 3 = http://theirserver.org/svn/eng-soft http://ourserver/viewvc/svn/$path/?pathrev=25914 116 114 4 = svn://anotherserver.com/tools_repository http://ourserver/tracs/tools/browser/$path?rev=$rev … … 122 120 Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. 123 121 124 === [ticket-custom] === #ticket-custom-section125 126 In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.127 128 === [ticket-workflow] === #ticket-workflow-section129 ''(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 137 122 ---- 138 123 See also: TracGuide, TracAdmin, TracEnvironment