Changes between Version 336 and Version 337 of TracInstall

Timestamp:

Feb 27, 2011, 3:47:22 PM (13 years ago)

Author:

Christian Boos

Comment:

Improve the #ScriptAlias-example

TracInstall

@@ -307 +307 @@
 
 
-===== Example: Apache and `ScriptAlias` =====
-
-Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WsgiScriptAlias` (which maps all the other requests to the Trac application), changing paths to match your deployment:
+===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example
+
+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:
 {{{
 Alias /trac/chrome/common /path/to/trac/htdocs/common
@@ -326 +326 @@
 }}}
 
-Note that we mapped `/trac` part of the URL to the `trac.cgi` script, and the path `/chrome/common` is the path you have to append to that location to intercept requests to the static resources. 
-
-For example, if Trac is mapped to `/cgi-bin/trac.cgi` on your server, the URL of the Alias should be `/cgi-bin/trac.cgi/chrome/common`, like so:
-
-{{{
-Alias /cgi-bin/trac.cgi/chrome/common /path/to/trac/htdocs/common
-}}}
-
-Similarly, if you have static resources in a project's htdocs directory (which is referenced by /chrome/site URL in themes), you can configure Apache to serve those resources (again, put this '''before''' the `ScriptAlias` for the CGI script, and adjust names and locations to match your installation):
+Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/chrome/common` is the path you have to append to that location to intercept requests to the static resources. 
+
+Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by /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):
 
 {{{
@@ -344 +338 @@
 }}}
 
-Alternatively to hacking `/trac/chrome/site`, you can directly specify path to static resources using `htdocs_location` configuration option in [wiki:TracIni trac.ini]:
+Alternatively to aliasing `/trac/chrome/common` and `/trac/chrome/site`, you can tell Trac to generate special links for those static resources, using the [[wiki:TracIni#trac-section| [trac] htdocs_location]] configuration setting:
 {{{
 [trac]
-htdocs_location = http://yourhost.example.org/trac-htdocs
-}}}
-
-Trac will then use this URL when embedding static resources into HTML pages. Of course, you still need to make the Trac `htdocs` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
+htdocs_location = http://static.example.org/trac-htdocs
+}}}
+Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).
+
+Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
 {{{
 $ ln -s /path/to/www/trac/htdocs /var/www/yourhost.example.org/trac-htdocs