| 296 | | Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance). |
| 297 | | |
| 298 | | Web servers such as [http://httpd.apache.org/ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself. |
| 299 | | |
| 300 | | There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything. |
| 301 | | |
| 302 | | Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the TracAdmin `deploy` command: |
| | 296 | Without additional configuration, Trac will handle requests for static resources such as stylesheets and images. For anything other than a TracStandalone deployment, this is not optimal as the web server can be set up to directly serve the static resources. For CGI setup, this is '''highly undesirable''' as it causes abysmal performance. |
| | 297 | |
| | 298 | Web servers such as [http://httpd.apache.org/ Apache] allow you to create //Aliases// to resources, giving them a virtual URL that doesn't necessarily reflect their location on the file system. We can map requests for static resources directly to directories on the file system, to avoid Trac processing the requests. |
| | 299 | |
| | 300 | There are two primary URL paths for static resources: `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible at the `/chrome/<plugin>` path. |
| | 301 | |
| | 302 | A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page. |
| | 303 | |
| | 304 | The resources are extracted using the [TracAdmin trac-admin]` <environment> deploy` command: |
| 305 | | The target `<directory>` will then contain an `htdocs` directory with: |
| 306 | | - `site/` - a copy of the environment's directory `htdocs/` |
| 307 | | - `common/` - the static resources of Trac itself |
| 308 | | - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment |
| 309 | | |
| 310 | | ===== Example: Apache and `ScriptAlias` #ScriptAlias-example |
| 311 | | |
| 312 | | Assuming the deployment has been done this way: |
| 313 | | {{{#!sh |
| 314 | | $ trac-admin /var/trac/env deploy /path/to/shared/trac |
| 315 | | }}} |
| 316 | | |
| 317 | | Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment: |
| | 307 | The target `<directory>` will contain an `htdocs` directory with: |
| | 308 | - `common/` - the static resources of Trac |
| | 309 | - `site/` - a copy of the environment's `htdocs/` directory |
| | 310 | - `shared` - the static resources shared by multiple Trac environments, with a location defined by the `[inherit]` `htdocs_dir` option |
| | 311 | - `<plugin>/` - one directory for each resource directory provided by the plugins enabled for this environment |
| | 312 | |
| | 313 | The example that follows will create a single `/chrome` alias. If that isn't the correct approach for your installation you simply need to create more specific aliases: |
| | 317 | Alias /trac/chrome/shared /path/to/trac/htdocs/shared |
| | 318 | Alias /trac/chrome/<plugin> /path/to/trac/htdocs/<plugin> |
| | 319 | }}} |
| | 320 | |
| | 321 | ===== Example: Apache and `ScriptAlias` #ScriptAlias-example |
| | 322 | |
| | 323 | Assuming the deployment has been done this way: |
| | 324 | {{{#!sh |
| | 325 | $ trac-admin /var/trac/env deploy /path/to/shared/trac |
| | 326 | }}} |
| | 327 | |
| | 328 | Add the following snippet to Apache configuration, changing paths to match your deployment. The snippet must be placed ''before'' the `ScriptAlias` or `WSGIScriptAlias` directive, because those directives map all requests to the Trac application: |
| | 329 | {{{#!apache |
| | 330 | Alias /trac/chrome /path/to/trac/htdocs |
| 342 | | Note that we mapped the `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources. |
| 343 | | |
| 344 | | Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation): |
| | 352 | Alternatively, if you wish to serve static resources directly from your project's `htdocs` directory rather than the location to which the files are extracted with the `deploy` command, you can configure Apache to serve those resources. Again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation: |
