Changes between Version 1 and Version 2 of TracIni

Nov 29, 2015, 3:00:01 AM (7 years ago)



  • TracIni

    v1 v2  
    1 = The Trac Configuration File =
     1= The Trac Configuration File
    5 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.
     6Trac is configured by editing the **`trac.ini`** file, located in the `<projectenv>/conf` directory. The `trac.ini` configuration file and its parent directory should be writable by the web server.
    7 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.
     8Trac monitors the timestamp of the file to trigger a complete environment reload and flush its caches when the timestamp changes. Most changes to the configuration will be 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 [#GlobalConfiguration global configuration] file when none was previously present.
    9 == Global Configuration ==
     10== Global Configuration
    11 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.
    13 Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:
    14 {{{
     12Configuration can be shared among environments using one or more global configuration files. Options in the global configuration will be merged with the environment-specific options, with local options overriding global options. The global configuration file is specified as follows:
    1615file = /path/to/global/trac.ini
    2221There 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.
     23Note 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, refresh your modifications when you upgrade to a new version of Trac. The preferred way to perform TracInterfaceCustomization is still to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation.
    2425== Reference for settings
    26 This is a brief reference of available configuration options.
     27This is a brief reference of available configuration options, and their default settings.
    28  ''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.''
     29Documentation improvements should be discussed on the [trac:MailingList#Trac-dev trac-dev mailing list] or described in a [trac:NewTicket ticket]. Even better, [trac:TracDev/SubmittingPatches submit a patch] against the docstrings in the code.
     30{{{ #!comment
     31Please don't waste your time by editing the HTML code below, changes won't be picked up. Instead, follow the above guidance for suggesting documentation improvements.
    32 == Reference for special sections
    33 [[PageOutline(3,,inline)]]
    35 === [components] === #components-section
    36 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.
    38 The option name is either the fully qualified name of the components or the module/package prefix of the component. The former enables/disables a specific component, while the latter enables/disables any component in the specified package/module.
    40 Consider the following configuration snippet:
    41 {{{
    42 [components]
    43 = disabled
    44 webadmin.* = enabled
    45 }}}
    47 The first option tells Trac to disable the [wiki:TracReports report module]. The second option instructs Trac to enable all components in the `webadmin` package. Note that the trailing wildcard is required for module/package matching.
    49 See the ''Plugins'' page on ''About Trac'' to get the list of active components (requires `CONFIG_VIEW` [wiki:TracPermissions permissions].)
    51 See also: TracPlugins
    53 === [milestone-groups] === #milestone-groups-section
    54 ''(since 0.11)''
    56 As the workflow for tickets is now configurable, there can be many ticket states,
    57 and simply displaying closed tickets vs. all the others is maybe not appropriate
    58 in all cases. This section enables one to easily create ''groups'' of states
    59 that will be shown in different colors in the milestone progress bar.
    61 Example configuration (the default only has closed and active):
    62 {{{
    63 closed = closed
    64 # sequence number in the progress bar
    65 closed.order = 0
    66 # optional extra param for the query (two additional columns: created and modified and sort on created)
    67 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
    68 # indicates groups that count for overall completion
    69 closed.overall_completion = truepercentage
    71 new = new
    72 new.order = 1
    73 new.css_class = new
    74 new.label = new
    76 # one catch-all group is allowed
    77 active = *
    78 active.order = 2
    79 # CSS class for this interval
    80 active.css_class = open
    81 # Displayed label for this group
    82 active.label = in progress
    83 }}}
    85 The definition consists in a comma-separated list of accepted status.
    86 Also, '*' means any status and could be used to associate all remaining
    87 states to one catch-all group.
    89 The CSS class can be one of: new (yellow), open (no color) or
    90 closed (green). New styles can easily be added using the following
    91 selector:  `table.progress td.<class>`
    93 === [repositories] === #repositories-section
    95 (''since 0.12'' multirepos)
    97 One of the alternatives for registering new repositories is to populate the `[repositories]` section of the trac.ini.
    99 This is especially suited for setting up convenience aliases, short-lived repositories, or during the initial phases of an installation.
    101 See [TracRepositoryAdmin#Intrac.ini TracRepositoryAdmin] for details about the format adopted for this section and the rest of that page for the other alternatives.
    103 === [svn:externals] === #svn:externals-section
    104 ''(since 0.11)''
    106 The TracBrowser for Subversion can interpret the `svn:externals` property of folders.
    107 By default, it only turns the URLs into links as Trac can't browse remote repositories.
    109 However, if you have another Trac instance (or an other repository browser like [ ViewVC]) configured to browse the target repository, then you can instruct Trac which other repository browser to use for which external URL.
    111 This mapping is done in the `[svn:externals]` section of the TracIni
    113 Example:
    114 {{{
    115 [svn:externals]
    116 1 = svn://server/repos1                       http://trac/proj1/browser/$path?rev=$rev
    117 2 = svn://server/repos2                       http://trac/proj2/browser/$path?rev=$rev
    118 3 =       http://ourserver/viewvc/svn/$path/?pathrev=25914
    119 4 = svn://  http://ourserver/tracs/tools/browser/$path?rev=$rev
    120 }}}
    121 With the above, the `svn://` 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 [ SVN Book on externals] for more details).
    123 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.
    125 Finally, the relative URLs introduced in [ Subversion 1.5] are not yet supported.
    127 === [ticket-custom] === #ticket-custom-section
    129 In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.
    131 === [ticket-workflow] === #ticket-workflow-section
    132 ''(since 0.11)''
    134 The workflow for tickets is controlled by plugins.
    135 By default, there's only a `ConfigurableTicketWorkflow` component in charge.
    136 That component allows the workflow to be configured via this section in the trac.ini file.
    137 See TracWorkflow for more details.