Changes between Version 6 and Version 7 of TracDev/TracURLs

Timestamp:

Feb 15, 2015, 8:26:42 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Reword.

TracDev/TracURLs

@@ -4 +4 @@
 
  /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].
- /chrome/site :: using this URL Trac accesses static resources for TracInterfaceCustomization that were uploaded to [TracEnvironment environment's] ''htdocs/'' directory 
- /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 [wiki:TracIni#inherit-section].
- /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
- /chrome/<pluginname> :: plugins may also have static resources that can be accessed using Trac chrome handler
+ /chrome/site :: accesses static resources for TracInterfaceCustomization contained in the [TracEnvironment environment's] ''htdocs/'' directory 
+ /chrome/shared :: accesses static resources in a shared location defined by the `htdocs_dir` option in the `inherit` section of the [wiki:TracIni#inherit-section].
+ /chrome/common :: accesses static resources used by Trac. These are usually found in the ''htdocs/'' subdirectory of the Trac installation.
+ /chrome/<pluginname> :: accesses static resources for a plugin
 
 All 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.