Changes between Version 4 and Version 5 of TracIni


Ignore:
Timestamp:
01/24/11 13:49:18 (15 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracIni

    v4 v5  
    11= The Trac Configuration File = 
     2 
    23[[TracGuideToc]] 
    34 
    … …  
    1314{{{ 
    1415[inherit] 
    15 file = /usr/share/trac/conf/trac.ini 
     16file = /path/to/global/trac.ini 
    1617}}} 
     18Multiple files can be specified using a comma-separated list. 
    1719 
    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. 
     20Note 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. 
    1921 
     22There 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. 
    2023 
    21 == Reference == 
     24Note 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). 
    2225 
    23 This is a brief reference of available configuration options. 
     26== Reference for settings 
     27 
     28This is a brief reference of available configuration options, and their default settings. 
    2429 
    2530 ''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.'' 
    2631 
    27 [[TracIni()]] 
     32[[TracIni]] 
    2833 
     34== Reference for special sections 
     35[[PageOutline(3,,inline)]] 
    2936 
    3037=== [components] === #components-section 
    … …  
    4653See also: TracPlugins 
    4754 
    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  
    6055=== [milestone-groups] === #milestone-groups-section 
    6156''(since 0.11)'' 
    … …  
    7368# optional extra param for the query (two additional columns: created and modified and sort on created) 
    7469closed.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 = truepercentage 
     70# indicates groups that count for overall completion percentage 
     71closed.overall_completion = true 
    7772 
    7873new = new 
    … …  
    9792closed (green). New styles can easily be added using the following 
    9893selector:  `table.progress td.<class>` 
     94 
     95=== [repositories] === #repositories-section 
     96 
     97(''since 0.12'' multirepos) 
     98 
     99One of the alternatives for registering new repositories is to populate the `[repositories]` section of the trac.ini. 
     100 
     101This is especially suited for setting up convenience aliases, short-lived repositories, or during the initial phases of an installation. 
     102 
     103See [TracRepositoryAdmin#Intrac.ini TracRepositoryAdmin] for details about the format adopted for this section and the rest of that page for the other alternatives. 
    99104 
    100105=== [svn:externals] === #svn:externals-section 
    … …  
    122127Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. 
    123128 
     129=== [ticket-custom] === #ticket-custom-section 
     130 
     131In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details. 
     132 
     133=== [ticket-workflow] === #ticket-workflow-section 
     134''(since 0.11)'' 
     135 
     136The workflow for tickets is controlled by plugins.  
     137By default, there's only a `ConfigurableTicketWorkflow` component in charge.  
     138That component allows the workflow to be configured via this section in the trac.ini file. 
     139See TracWorkflow for more details. 
     140 
    124141---- 
    125142See also: TracGuide, TracAdmin, TracEnvironment