Changes between Version 2 and Version 3 of TracCgi


Ignore:
Timestamp:
18/06/13 12:48:03 (8 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracCgi

    v2 v3  
    11= Installing Trac as CGI =
    22
    3 To install Trac as a CGI script, you need to make the `trac.cgi` executable as a CGI by your web server.
     3{{{
     4#!div class=important
     5  ''Please note that using Trac via CGI is the slowest deployment method available. It is slower than [TracModPython mod_python], [TracFastCgi FastCGI] and even [trac:TracOnWindowsIisAjp IIS/AJP] on Windows.''
     6}}}
    47
    5   ''Please note that using Trac via CGI is significantly slower than any other deployment method, such as [TracModPython mod_python] or [TracFastCgi FastCGI].''
     8CGI script is the entrypoint that web-server calls when a web-request to an application is made. To generate the `trac.cgi` script run:
     9{{{
     10trac-admin /path/to/env deploy /path/to/www/trac
     11}}}
     12`trac.cgi` will be in the `cgi-bin` folder inside the given path. ''Make sure it is executable by your web server''. This command also copies `static resource` files to a `htdocs` directory of a given destination.
    613
    7 If you're using [http://httpd.apache.org/ Apache HTTPD], there are a couple ways to do that:
     14== Apache web-server configuration ==
    815
    9  1. Use a `ScriptAlias` to map a URL to the `trac.cgi` script
     16In [http://httpd.apache.org/ Apache] there are two ways to run Trac as CGI:
     17
     18 1. Use a `ScriptAlias` directive that maps an URL to the `trac.cgi` script (recommended)
    1019 2. Copy the `trac.cgi` file into the directory for CGI executables used by your web server (commonly named `cgi-bin`). You can also create a symbolic link, but in that case make sure that the `FollowSymLinks` option is enabled for the `cgi-bin` directory.
    1120
    12 The first option is recommended as it also allows you to map the CGI to a friendly URL.
    13 
    14 Now, edit the Apache configuration file and add this snippet, file names and locations changed to match your installation:
     21To make Trac available at `http://yourhost.example.org/trac` add `ScriptAlias` directive to Apache configuration file, changing `trac.cgi` path to match your installation:
    1522{{{
    16 ScriptAlias /trac /usr/share/trac/cgi-bin/trac.cgi
     23ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.cgi
    1724}}}
    1825
    19  ''Note that this directive requires the `mod_alias` module to be installed and enabled.''
     26 ''Note that this directive requires enabled `mod_alias` module.''
    2027
    2128If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable:
     
    3340}}}
    3441
    35  ''Note that the `SetEnv` directive requires the `mod_env` module to be installed and enable. If not, you could set TRAC_ENV in trac.cgi. Just add the following code between "try:" and "from trac.web ...":''
     42 ''Note that the `SetEnv` directive requires enabled `mod_env` module. It is also possible to set TRAC_ENV in trac.cgi. Just add the following code between "try:" and "from trac.web ...":''
    3643
    3744{{{
     
    4754}}}
    4855
    49 This will make Trac available at `http://yourhost.example.org/trac`.
    50 
    5156If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [http://trac.edgewall.org/wiki/ApacheSuexec].
    5257
    5358On some systems, you ''may'' need to edit the shebang line in the `trac.cgi` file to point to your real Python installation path. On a Windows system you may need to configure Windows to know how to execute a .cgi file (Explorer -> Tools -> Folder Options -> File Types -> CGI).
    5459
     60=== Using WSGI ===
     61
     62You can run a [http://henry.precheur.org/python/how_to_serve_cgi WSGI handler] [http://pythonweb.org/projects/webmodules/doc/0.5.3/html_multipage/lib/example-webserver-web-wsgi-simple-cgi.html under CGI].  You can [wiki:TracModWSGI#Thetrac.wsgiscript write your own application function], or use the deployed trac.wsgi's application.
     63
    5564== Mapping Static Resources ==
    5665
    57 Out of the box, Trac will serve static resources such as style sheets or images itself. For a CGI setup, though, this is highly undesirable, because it results in the CGI script being invoked for documents that could be much more efficiently served by the web server directly.
    58 
    59 Web servers such as [http://httpd.apache.org/ Apache HTTPD] allow you to create “Aliases” to resources, thereby giving them a virtual URL that doesn't necessarily bear any resemblance to the layout of the servers file system. We already used this capability above when defining a `ScriptAlias` for the CGI script, and we'll use it now to map requests to the static resources to the directory on the file system that contains them, thereby bypassing the processing of such requests by the CGI script.
    60 
    61 Edit the Apache configuration file again and add the following snippet '''before''' the `ScriptAlias` for the CGI script , file names and locations changed to match your installation:
    62 {{{
    63 Alias /trac/chrome/common /usr/share/trac/htdocs
    64 <Directory "/usr/share/trac/htdocs">
    65   Order allow,deny
    66   Allow from all
    67 </Directory>
    68 }}}
    69 
    70 Note that whatever URL path you mapped the `trac.cgi` script to, the path `/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
    71 
    72 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`.
    73 
    74 Similarly, if you have static resources in a projects htdocs directory, 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):
    75 
    76 {{{
    77 Alias /trac/chrome/site /path/to/projectenv/htdocs
    78 <Directory "/path/to/projectenv/htdocs">
    79   Order allow,deny
    80   Allow from all
    81 </Directory>
    82 }}}
    83 
    84 Alternatively, you can set the `htdocs_location` configuration option in [wiki:TracIni trac.ini]:
    85 {{{
    86 [trac]
    87 htdocs_location = /trac-htdocs
    88 }}}
    89 
    90 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:
    91 {{{
    92 $ ln -s /usr/share/trac/htdocs /var/www/your_site.com/htdocs/trac-htdocs
    93 }}}
     66See TracInstall#MappingStaticResources.
    9467
    9568== Adding Authentication ==
    9669
    97 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file:
    98 {{{
    99 $ htpasswd -c /somewhere/trac.htpasswd admin
    100 New password: <type password>
    101 Re-type new password: <type password again>
    102 Adding password for user admin
    103 }}}
    104 
    105 After the first user, you dont need the "-c" option anymore:
    106 {{{
    107 $ htpasswd /somewhere/trac.htpasswd john
    108 New password: <type password>
    109 Re-type new password: <type password again>
    110 Adding password for user john
    111 }}}
    112 
    113   ''See the man page for `htpasswd` for full documentation.''
    114 
    115 After you've created the users, you can set their permissions using TracPermissions.
    116 
    117 Now, you'll need to enable authentication against the password file in the Apache configuration:
    118 {{{
    119 <Location "/trac/login">
    120   AuthType Basic
    121   AuthName "Trac"
    122   AuthUserFile /somewhere/trac.htpasswd
    123   Require valid-user
    124 </Location>
    125 }}}
    126 
    127 If you're hosting multiple projects you can use the same password file for all of them:
    128 {{{
    129 <LocationMatch "/trac/[^/]+/login">
    130   AuthType Basic
    131   AuthName "Trac"
    132   AuthUserFile /somewhere/trac.htpasswd
    133   Require valid-user
    134 </LocationMatch>
    135 }}}
    136 
    137 For better security, it is recommended that you either enable SSL or at least use the “Digest” authentication scheme instead of “Basic”. Please read the [http://httpd.apache.org/docs/2.0/ Apache HTTPD documentation] to find out more. For example, on a Debian 4.0r1 (etch) system the relevant section  in apache configuration can look like this:
    138 {{{
    139 <Location "/trac/login">
    140     LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
    141     AuthType Digest
    142     AuthName "trac"
    143     AuthDigestDomain /trac
    144     AuthUserFile /somewhere/trac.htpasswd
    145     Require valid-user
    146 </Location>
    147 }}}
    148 and you'll have to create your .htpasswd file with htdigest instead of htpasswd as follows:
    149 {{{
    150 # htdigest /somewhere/trac.htpasswd trac admin
    151 }}}
    152 where the "trac" parameter above is the same as !AuthName above  ("Realm" in apache-docs).
     70See TracInstall#ConfiguringAuthentication.
    15371
    15472----
    155 See also:  TracGuide, TracInstall, TracFastCgi, TracModPython
     73See also:  TracGuide, TracInstall, [wiki:TracModWSGI], TracFastCgi, TracModPython