| 3 | | * [/chrome /chrome] - the handler for this URL just serves files that are placed in `htdocs` folder of [TracEnvironment Trac environment]. |
| 4 | | These files are usually images, CSS and .js that are called ''static resources'', because they won't require any server-side processing. In fact to avoid firing [TracDev/RequestHandling Trac request handling] many prefer setup when static resources are [TracCgi#MappingStaticResources served by web server] directly. |
| | 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 | |
| | 5 | * [/chrome/site /chrome/site] - using this URL Trac accesses static resources for TracInterfaceCustomization that were uploaded to [TracEnvironment environment's] ''htdocs/'' directory |
| | 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 | |
| | 8 | * /chrome/<pluginname> - plugins may also have static resources that can be accessed using Trac chrome handler |
| | 9 | |
| | 10 | 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. |
