Changes between Version 1 and Version 2 of TracCgi


Ignore:
Timestamp:
Apr 13, 2011, 7:00:48 PM (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracCgi

    v1 v2  
    6464Web 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.
    6565
     66There 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
    6668Add the following snippet to Apache configuration '''before''' the `ScriptAlias` for the CGI script, changing paths to match your deployment:
    6769{{{
    68 Alias /trac/chrome/common /path/to/www/trac/htdocs
     70Alias /trac/chrome/common /path/to/trac/htdocs/common
     71Alias /trac/chrome/site /path/to/trac/htdocs/site
    6972<Directory "/path/to/www/trac/htdocs">
    7073  Order allow,deny
    7174  Allow from all
    7275</Directory>
     76}}}
     77
     78If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
     79{{{
     80<Location "/trac/chrome/common/">
     81  SetHandler None
     82</Location>
    7383}}}
    7484