Edgewall Software

Changes between Version 199 and Version 200 of TracIni


Ignore:
Timestamp:
Mar 1, 2015, 8:45:08 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracIni

    v199 v200  
    1 = The Trac Configuration File =
     1= The Trac Configuration File
    22
    3  ''[Note To Editors] Please discuss documentation changes in the [#Discussion] section. Even better, send us [trac:TracDev/SubmittingPatches documentation patches] against the ''code'' (i.e. where the configuration entries are documented), either on Trac-dev or on new tickets. ''
     3'''[Note To Editors]''' Please discuss documentation changes in the [#Discussion] section. Even better, send us [trac:TracDev/SubmittingPatches documentation patches] against the ''code'', ie where the configuration entries are documented, either on Trac-dev or on new tickets.
    44
    55[[TracGuideToc]]
    … …  
    1010The `trac.ini` configuration file and its parent directory should be writable by the web server, as Trac currently relies on the possibility to trigger a complete environment reload to flush its caches.
    1111
    12 == Global Configuration ==
     12== Global Configuration
    1313
    1414In 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.
    … …  
    2525There 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.
    2626
    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).
     27Note 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.
    2828
    2929== Reference for settings
    … …  
    4343[[TracIni]]
    4444
    45 == Discussion ==
    46 ''Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.''
     45== Discussion
    4746
     47Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.
    4848
    4949----