Changes between Initial Version and Version 1 of TracCgi

Show
Ignore:
Timestamp:
10/06/08 18:48:48 (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracCgi

    v1 v1  
     1= Installing Trac as CGI = 
     2 
     3To install Trac as a CGI script, you need to make the `trac.cgi` executable as a CGI by your web server. 
     4 
     5  ''Please note that using Trac via CGI is significantly slower than any other deployment method, such as [TracModPython mod_python] or [TracFastCgi FastCGI].'' 
     6 
     7If you're using [http://httpd.apache.org/ Apache HTTPD], there are a couple ways to do that: 
     8 
     9 1. Use a `ScriptAlias` to map a URL to the `trac.cgi` script 
     10 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. 
     11 
     12The first option is recommended as it also allows you to map the CGI to a friendly URL. 
     13 
     14Now, edit the Apache configuration file and add this snippet, file names and locations changed to match your installation: 
     15{{{ 
     16ScriptAlias /trac /usr/share/trac/cgi-bin/trac.cgi 
     17}}} 
     18 
     19 ''Note that this directive requires the `mod_alias` module to be installed and enabled.'' 
     20 
     21If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable: 
     22{{{ 
     23<Location "/trac"> 
     24  SetEnv TRAC_ENV "/path/to/projectenv" 
     25</Location> 
     26}}} 
     27 
     28Or to use multiple projects you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` variable: 
     29{{{ 
     30<Location "/trac"> 
     31  SetEnv TRAC_ENV_PARENT_DIR "/path/to/project/parent/dir" 
     32</Location> 
     33}}} 
     34 
     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 ...":'' 
     36 
     37{{{ 
     38    import os 
     39    os.environ['TRAC_ENV'] = "/path/to/projectenv" 
     40}}} 
     41 
     42 '' Or for TRAC_ENV_PARENT_DIR: '' 
     43 
     44{{{ 
     45    import os 
     46    os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir" 
     47}}} 
     48 
     49This will make Trac available at `http://yourhost.example.org/trac`. 
     50 
     51If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [http://trac.edgewall.org/wiki/ApacheSuexec]. 
     52 
     53On 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). 
     54 
     55== Mapping Static Resources == 
     56 
     57Out 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 
     59Web 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 
     61Edit 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{{{ 
     63Alias /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 
     70Note 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 
     72For 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 
     74Similarly, 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{{{ 
     77Alias /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 
     84Alternatively, you can set the `htdocs_location` configuration option in [wiki:TracIni trac.ini]: 
     85{{{ 
     86[trac] 
     87htdocs_location = /trac-htdocs 
     88}}} 
     89 
     90Trac 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}}} 
     94 
     95Note that in order to get this `htdocs` directory, you need first to extract the relevant Trac resources using the `deploy` command of TracAdmin: 
     96[[TracAdminHelp(deploy)]] 
     97 
     98 
     99== Adding Authentication == 
     100 
     101The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file: 
     102{{{ 
     103$ htpasswd -c /somewhere/trac.htpasswd admin 
     104New password: <type password> 
     105Re-type new password: <type password again> 
     106Adding password for user admin 
     107}}} 
     108 
     109After the first user, you dont need the "-c" option anymore: 
     110{{{ 
     111$ htpasswd /somewhere/trac.htpasswd john 
     112New password: <type password> 
     113Re-type new password: <type password again> 
     114Adding password for user john 
     115}}} 
     116 
     117  ''See the man page for `htpasswd` for full documentation.'' 
     118 
     119After you've created the users, you can set their permissions using TracPermissions. 
     120 
     121Now, you'll need to enable authentication against the password file in the Apache configuration: 
     122{{{ 
     123<Location "/trac/login"> 
     124  AuthType Basic 
     125  AuthName "Trac" 
     126  AuthUserFile /somewhere/trac.htpasswd 
     127  Require valid-user 
     128</Location> 
     129}}} 
     130 
     131If you're hosting multiple projects you can use the same password file for all of them: 
     132{{{ 
     133<LocationMatch "/trac/[^/]+/login"> 
     134  AuthType Basic 
     135  AuthName "Trac" 
     136  AuthUserFile /somewhere/trac.htpasswd 
     137  Require valid-user 
     138</LocationMatch> 
     139}}} 
     140 
     141For 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: 
     142{{{ 
     143<Location "/trac/login"> 
     144    LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so 
     145    AuthType Digest 
     146    AuthName "trac" 
     147    AuthDigestDomain /trac 
     148    AuthDigestFile /somewhere/trac.htpasswd 
     149    Require valid-user 
     150</Location> 
     151}}} 
     152and you'll have to create your .htpasswd file with htdigest instead of htpasswd as follows: 
     153{{{ 
     154# htdigest /somewhere/trac.htpasswd trac admin 
     155}}} 
     156where the "trac" parameter above is the same as !AuthName above  ("Realm" in apache-docs).  
     157 
     158---- 
     159See also:  TracGuide, TracInstall, TracFastCgi, TracModPython