Changes between Version 5 and Version 6 of TracIni


Ignore:
Timestamp:
Feb 26, 2008 5:40:01 PM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracIni

    v5 v6  
    22[[TracGuideToc]]
    33
    4 Trac configuration is done by editing the '''`trac.ini`''' config file, located in `<projectenv>/conf/trac.ini`.
     4Trac 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.
    55
    66== Global Configuration ==
    77
    8 Since version 0.9, Trac can also read the configuration from a global `trac.ini` file. These global options will then be merged with the environment-specific options, where local options override global options.
     8In previous versions, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or sometimes /etc/trac/trac.ini depending on the distribution. If you're upgrading, you may want to specify that file to inherit from.
    99
    10 The global configuration is by default localted in `$prefix/share/trac/conf/trac.ini`. It can be moved to a different location (for example, `/etc/trac.ini`), but that requires changing the file `trac/siteconfig.py` which gets created when Trac is installed.
     10Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:
     11{{{
     12[inherit]
     13file = /usr/share/trac/conf/trac.ini
     14}}}
    1115
    1216== Reference ==
     
    1620[[TracIni]]
    1721
    18 == [components] ==
    19 (''since 0.9'')
    20 
     22== [components] == #components-section
    2123This 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.
    2224
     
    3638See also: TracPlugins
    3739
    38   ''Note that prior to Trac r2335 (that applies to 0.9b1 and 0.9b2), you would use a `[disabled_components]` section instead. See a [http://projects.edgewall.com/trac/wiki/TracIni?version=42 previous version] of this page for the details.''
     40== [ticket-custom] == #ticket-custom-section
     41
     42In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.
     43
     44== [ticket-workflow] == #ticket-workflow-section
     45''(since 0.11)''
     46
     47The workflow for tickets is controlled by plugins.
     48By default, there's only a `ConfigurableTicketWorkflow` component in charge.
     49That component allows the workflow to be configured via this section in the trac.ini file.
     50See TracWorkflow for more details.
     51
     52== [milestone-groups] == #milestone-groups-section
     53''(since 0.11)''
     54
     55As the workflow for tickets is now configurable, there can be many ticket states,
     56and simply displaying closed tickets vs. all the others is maybe not appropriate
     57in all cases. This section enables one to easily create ''groups'' of states
     58that will be shown in different colors in the milestone progress bar.
     59
     60Example configuration (which is also the default):
     61{{{
     62closed = closed
     63closed.order = 0                     # sequence number in the progress bar
     64closed.query_args = group=resolution # optional extra param for the query
     65closed.overall_completion = true     # count for overall completion
     66
     67active = *                           # one catch-all group is allowed
     68active.order = 1
     69active.css_class = open              # CSS class for this interval
     70}}}
     71
     72The definition consists in a comma-separated list of accepted status.
     73Also, '*' means any status and could be used to associate all remaining
     74states to one catch-all group.
     75
     76The CSS class can be one of: new (yellow), open (no color) or
     77closed (green). New styles can easily be added using the following
     78selector:  `table.progress td.<class>`
     79
     80== [svn:externals] == #svn:externals-section
     81''(since 0.11)''
     82
     83The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box.
     84However, if those externals are ''not'' using the `http:` protocol, or if a link to a different repository browser (such 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.
     85
     86This mapping is done in the `[svn:externals]` section of the TracIni
     87
     88Example:
     89{{{
     90[svn:externals]
     91http://theirserver.org/svn/eng-soft       http://ourserver/viewvc/svn/$path/?pathrev=25914
     92svn://anotherserver.com/tools_repository  http://ourserver/trac/support/browser/$path?rev=$rev
     93}}}
     94With the above, the `svn://anotherserver.com/tools_repository/tags/1.1/tools` external will be mapped to `http://ourserver/trac/support/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 [http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html SVN Book on externals] for more details).
     95
    3996
    4097----
    4198See also: TracGuide, TracAdmin, TracEnvironment
    42