COIN-OR::LEMON - Graph Library

Changes between Version 1 and Version 2 of TracIni

06/30/08 15:21:27 (16 years ago)



  • TracIni

    v1 v2  
    11= The Trac Configuration File =
    4 Trac configuration is done by editing the '''`trac.ini`''' config file, located in `<projectenv>/conf/trac.ini`.
    65== Global Configuration ==
    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.
     7In versions prior to 0.11, 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.
    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/` which gets created when Trac is installed.
     9Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:
     12file = /usr/share/trac/conf/trac.ini
     15Note that you can also specify a global option file when creating a new project,  by adding the option
     16`--inherit=/path/to/global/options` to [TracAdmin trac-admin]'s `initenv` command.
     17If you would not do this but nevertheless intend to use a global option file with your new environment,
     18you would have to go through the newly generated conf/trac.ini file and delete the entries that would
     19otherwise override those set in the global file.
    1222== Reference ==
    1424This is a brief reference of available configuration options.
    16 [[TracIni]]
    18 == [components] ==
    19 (''since 0.9'')
     29== [components] == #components-section
    2130This 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.
    3645See also: TracPlugins
    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 [ previous version] of this page for the details.''
     47== [ticket-custom] == #ticket-custom-section
     49In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.
     51== [ticket-workflow] == #ticket-workflow-section
     52''(since 0.11)''
     54The workflow for tickets is controlled by plugins.
     55By default, there's only a `ConfigurableTicketWorkflow` component in charge.
     56That component allows the workflow to be configured via this section in the trac.ini file.
     57See TracWorkflow for more details.
     59== [milestone-groups] == #milestone-groups-section
     60''(since 0.11)''
     62As the workflow for tickets is now configurable, there can be many ticket states,
     63and simply displaying closed tickets vs. all the others is maybe not appropriate
     64in all cases. This section enables one to easily create ''groups'' of states
     65that will be shown in different colors in the milestone progress bar.
     67Example configuration (which is also the default):
     69closed = closed
     70closed.order = 0                     # sequence number in the progress bar
     71closed.query_args = group=resolution # optional extra param for the query
     72closed.overall_completion = true     # count for overall completion
     74active = *                           # one catch-all group is allowed
     75active.order = 1
     76active.css_class = open              # CSS class for this interval
     77active.label = in progress           # Displayed label for this group
     80The definition consists in a comma-separated list of accepted status.
     81Also, '*' means any status and could be used to associate all remaining
     82states to one catch-all group.
     84The CSS class can be one of: new (yellow), open (no color) or
     85closed (green). New styles can easily be added using the following
     86selector:  `table.progress td.<class>`
     88== [svn:externals] == #svn:externals-section
     89''(since 0.11)''
     91The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box.
     92However, if those externals are ''not'' using the `http:` protocol, or if a link to a different repository browser (such another Trac or [ ViewVC]) is desired, then Trac needs to be able to map an external prefix to this other URL.
     94This mapping is done in the `[svn:externals]` section of the TracIni
     991 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev
     1002 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev
     1013 =       http://ourserver/viewvc/svn/$path/?pathrev=25914
     1024 = svn://  http://ourserver/trac/support/browser/$path?rev=$rev
     104With the above, the `svn://` 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 [ SVN Book on externals] for more details).
     106Note 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.
    41109See also: TracGuide, TracAdmin, TracEnvironment