Changes between Version 1 and Version 2 of TracCgi
- Timestamp:
- 2010-10-01T18:22:04Z (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracCgi
v1 v2 64 64 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 already used this capability by defining a `ScriptAlias` for the CGI script. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by CGI script. 65 65 66 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. 67 66 68 Add the following snippet to Apache configuration '''before''' the `ScriptAlias` for the CGI script, changing paths to match your deployment: 67 69 {{{ 68 Alias /trac/chrome/common /path/to/ www/trac/htdocs70 Alias /trac/chrome/common /path/to/trac/htdocs 69 71 <Directory "/path/to/www/trac/htdocs"> 70 72 Order allow,deny