Changes between Version 2 and Version 3 of TracLitespeed

Timestamp:

Feb 21, 2015, 11:24:49 AM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracLitespeed

@@ -1 @@
-= Basic Multiproject under Litespeed =
+= Basic Multiproject under Litespeed
 
 This document specifies how to modify an existing Trac setup to work with [http://litespeedtech.com/ Litespeed]. It assumes you have a working Trac install which can serve single Trac projects using the tracd server.
 
-This document assumes some default paths, such as
+This document assumes some default paths for the basic Trac installation, such as:
  * /usr/share/trac/
  * /usr/lib/python-[ver]/site-packages/trac/
-for the basic Trac installation.
 
-This document _also_ assumes you wish to setup Trac to use a dedicated subdomain. It should be trivial, however, to change this behaviour.
+This document also assumes you wish to setup Trac to use a dedicated subdomain. It should be trivial to change this behavior however.
 
-== Allowing project-based URL's in Trac ==
+== Allowing project-based URL's in Trac
 
-Edit the Trac main.py file. On Linux this file can be found in /usr/lib/python-[ver]/site-packages/trac/web/main.py where [ver] is replaced with your python version (such as 2.4).
+Edit the Trac main.py file. On Linux this file can be found in /usr/lib/python-[x.y]/site-packages/trac/web/main.py where [x.y] is replaced with your Python version (such as 2.4).
 
-Replace the line
+Replace the line:
 {{{
 env.href = Href(req.cgi_location)
 }}}
-with
+with:
 {{{
 env.href = Href(req.base_url)
 }}}
-save and exit
 
-This modification allows Trac to generate URL's based on the __project path__ rather than the cgi path.
+This modification allows Trac to generate URL's based on the '''project path''' rather than the '''CGI path'''.
 
-You will also need to add the following line to each of your project's trac.ini files manually.
-
-Under [trac] add
+Edit the trac.ini file. Under [trac] add:
 {{{
 base_url = /projects/[projectname]
 }}}
 
-The following example will make the 'test' project accessable at http://yourdomain.tld/projects/test
+The following example will make the 'test' project accessable at http://yourdomain.tld/projects/test:
 {{{
 base_url = /projects/test
 }}}
 
-== Creating Litespeed Config ==
+== Creating the Litespeed Config
 
-Using the Litespeed configuration panel
+Using the Litespeed configuration panel:
 
  * Create a Trac virtual host 
@@ -50 +46 @@
 RewriteRule ^/projects/(.*)                     /index.html
 }}}
- * Add a Static context with the following
+ * Add a Static context with the following:
    * URI: /trac.cgi/chrome/common
    * Location: /usr/share/trac/htdocs
@@ -56 +52 @@
    * Enable Expires: No
 
- * Create a CGI context with the following
+ * Create a CGI context with the following:
    * URI: /
    * Path: /usr/share/trac/cgi-bin/
@@ -62 +58 @@
  * Save and reload Litespeed
 
-This will make project accessable through the address
+This will make project accessable through the address:
 {{{
 http://subdomain.domain.tld/projects/[projectname]
 }}}
 
-== Basic Security ==
+== Basic Security
 
-To set up a basic catch-all security net for your projects, simply follow this guide
+To set up a basic catch-all security net for your projects, simply follow this guide:
 
  * Create a new security realm using the Litespeed config and point it to your Password file.
-   * Don't have one, use http://sherylcanter.com/encrypt.php to generate username:password combos.
+   * If you don't have one, use http://sherylcanter.com/encrypt.php to generate username:password combos.
  * Assign the security realm to the Trac CGI context.
  * Trac will be able understand this security context.
+
+----
+See also: BloodHound