Changes between Version 6 and Version 7 of 0.12/TracIni
- Timestamp:
- Jan 6, 2011, 5:29:31 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracIni
v6 v7 1 ** Note: this page was used to prepare the 0.12 version of wiki:/TracIni, see now directly that toplevel page**1 ** Note: this page documents the 0.12 version of Trac, see [[0.11/TracIni]] if you need the previous version ** 2 2 = The Trac Configuration File = 3 3 4 ''[Note To Editors] Please discuss documentation changes in the [#Discussion] section. Even better, send us documentation patchesagainst the ''code'' (i.e. where the configuration entries are documented), either on Trac-dev or on new tickets. ''4 ''[Note To Editors] Please discuss documentation changes in the [#Discussion] section. Even better, send us [TracDev/SubmittingPatches documentation patches] against the ''code'' (i.e. where the configuration entries are documented), either on Trac-dev or on new tickets. '' 5 5 6 6 [[TracGuideToc]] … … 17 17 {{{ 18 18 [inherit] 19 file = / usr/share/trac/conf/trac.ini19 file = /path/to/global/trac.ini 20 20 }}} 21 Multiple files can be specified using a comma-separated list. 21 22 22 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.inifile and delete the entries that will otherwise override those set in the global file.23 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. 23 24 25 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. 26 27 Note that the templates found in the `templates/` directory of the TracEnvironment have precedence over those found in `[inherit] templates_dir`. In turn, the latter have precedence over the installed templates, so be careful about what you put there, notably if you override a default template be sure to refresh your modifications when you upgrade to a new version of Trac (the preferred way to perform TracInterfaceCustomization being still to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation). 24 28 25 29 == Reference for settings 26 30 27 This is a brief reference of available configuration options .31 This is a brief reference of available configuration options, and their default settings. 28 32 29 33 ''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.'' … … 73 77 # optional extra param for the query (two additional columns: created and modified and sort on created) 74 78 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 # indicates groups that count for overall completion 76 closed.overall_completion = true percentage79 # indicates groups that count for overall completion percentage 80 closed.overall_completion = true 77 81 78 82 new = new … … 147 151 ''Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.'' 148 152 149 * There is, apparently, an [svn] `repository_url` option that is not documented here. [[br]]150 No, there's no such thing. There ''might'' be a plugin providing support for this, for Trac 0.12. However, Trac 0.12 will support an `url` property for repositories.151 * It can be helpful to know the default values for each entry, perhaps specified in a common format such as square brackets [] at the end of the description (or at the beginning of the description). ''for 0.12?''152 153 153 154 154 ----