Changes between Version 16 and Version 17 of 0.12/TracInstall
- Timestamp:
- Apr 5, 2010, 10:07:26 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracInstall
v16 v17 206 206 == Running Trac on a Web Server == 207 207 208 Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi.208 Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi. 209 209 210 210 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. 211 211 212 212 ==== Generating the Trac cgi-bin directory ==== 213 {{{#!div style="background:#efe" 214 MMM: If I understand correctly mod_wsgi is preferred over mod_python. Does the section below apply to mod_wsgi also? 215 }}} 216 217 In order for Trac to function properly with FastCGI or mod_python, you need to have a trac.cgi file. This is an executable which loads the appropriate Python code. It can be generated using the `deploy` option of [wiki:TracAdmin trac-admin]. 213 214 In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin]. 218 215 219 216 There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this: