Edgewall Software

Changes between Version 3 and Version 4 of TracDev/TracURLs


Ignore:
Timestamp:
Feb 28, 2011, 10:37:53 AM (13 years ago)
Author:
Christian Boos
Comment:

clean-up and corrections

Legend:

Unmodified
Added
Removed
Modified

  • TracDev/TracURLs

    v3 v4  
    1 Trac has some ''unusual'' or better said ''special'' conventions about default URL paths (or URL endpoints). These are specified relative to base Trac URL.
     1The following URLs are specified relative to base Trac URL:
    22
    3 * [/chrome /chrome] - the handler for this URL just serves files that are placed in `htdocs` folder of [TracEnvironment Trac environment].  [[BR]] [[BR]] These files are usually ''images'', ''.css'' and ''.js'' that are called ''static resources'', because they don't require any server-side processing and can be served as-is. In fact to avoid firing [TracDev/RequestHandling Trac request handling] many people prefer setups when static resources are [TracCgi#MappingStaticResources served by web server] directly.
    4 * [/chrome/site /chrome/site] - using this URL Trac accesses static resources for TracInterfaceCustomization that were uploaded to [TracEnvironment environment's] ''htdocs/'' directory
    5 * /chrome/shared - using this URL Trac accesses static resources in a shared location defined by the `htdocs_dir` option in the `inherit` section of the TracIni.
    6 * [/chrome/common /chrome/common] - with this URL Trac accesses static resources used by default Trac scheme - these are usually found in ''htdocs/'' subdirectory in Trac installation location
    7 * /chrome/<pluginname> - plugins may also have static resources that can be accessed using Trac chrome handler
     3 /chrome :: for any kind of ''static resources'' (usually ''images'', ''.css'' and ''.js''). They are called ''static'', because they don't require any server-side processing and can be served as-is. In fact to avoid firing [TracDev/RequestHandling Trac request handling] many people prefer to have those static resources  [TracInstall#MappingStaticResources served directly by the web server].
     4 /chrome/site :: using this URL Trac accesses static resources for TracInterfaceCustomization that were uploaded to [TracEnvironment environment's] ''htdocs/'' directory
     5 /chrome/shared :: using this URL Trac accesses static resources in a shared location defined by the `htdocs_dir` option in the `inherit` section of the TracIni.
     6 /chrome/common :: with this URL Trac accesses static resources used by default Trac scheme - these are usually found in ''htdocs/'' subdirectory in Trac installation location
     7 /chrome/<pluginname> :: plugins may also have static resources that can be accessed using Trac chrome handler
    88
    9 All static resources can be exported with '''trac-admin deploy''' command to serve them independently. The process is described in detail on TracCgi#MappingStaticResources page. Just do not forget to re-export them after installing new plugins or upgrading Trac.
     9All static resources can be exported with '''trac-admin deploy''' command to serve them independently. The process is described in detail in TracInstall#MappingStaticResources. Just do not forget to re-export them after installing new plugins or upgrading Trac.