Changes between Version 9 and Version 10 of TracFastCgi
- Timestamp:
- Dec 14, 2014, 5:16:20 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFastCgi
v9 v10 1 [[PageOutline]]2 3 1 = Trac with FastCGI = 4 2 5 [http://www.fastcgi.com/ FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python] or [wiki:TracModWSGI mod_wsgi]. It is faster than external CGI interfaces which must start a new process for each request. Additionally, it is supported by much wider variety of web servers. 6 7 Note that unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], i.e. run with different permissions than web server running with (`mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect). 8 9 '''Note for Windows:''' Trac's FastCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, you may want to try [trac:TracOnWindowsIisAjp AJP]/[trac:TracOnWindowsIisAjp ISAPI]. 10 11 [[PageOutline(2-3,Overview,inline)]] 12 3 [http://www.fastcgi.com/ FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python]. It is faster than external CGI interfaces which must start a new process for each request. However, unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], i.e. run with different permissions than web server. Additionally, it is supported by much wider variety of web servers. 4 5 '''Note for Windows:''' Trac's FastCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, you may want to try [trac:TracOnWindowsIisAjp AJP]. 13 6 14 7 == Simple Apache configuration == … … 17 10 `mod_fcgid` (preferred). The latter is more up-to-date. 18 11 19 The following sections focus on the FCGI specific setup, see also [wiki:TracModWSGI#ConfiguringAuthentication] for configuring the authentication in Apache. 20 21 Regardless of which cgi module is used, be sure the web server has executable permissions on the cgi-bin folder. While FastCGI will throw specific permissions errors, mod_fcgid will throw an ambiguous error if this has not been done. (Connection reset by peer: mod_fcgid: error reading data from FastCGI server) 22 23 === Set up with `mod_fastcgi` === 12 ==== setup with `mod_fastcgi` ==== 24 13 `mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file: 25 14 {{{ … … 38 27 calling `trac.fcgi` instead of `trac.cgi`. 39 28 40 Add the following to the Apache configuration file (below the `FastCgiIpcDir` line) if you intend toset up the `TRAC_ENV` as an overall default:29 You can set up the `TRAC_ENV` as an overall default: 41 30 {{{ 42 31 FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac 43 32 }}} 44 33 45 Alternatively, you can serve multiple Trac projects in a directory by adding this:34 Or you can serve multiple Trac projects in a directory like: 46 35 {{{ 47 36 FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects 48 37 }}} 49 38 50 === Set up with `mod_fcgid`===39 ==== setup with `mod_fcgid` ==== 51 40 Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` 52 41 instead of `trac.cgi`. Note that slash at the end - it is important. … … 55 44 }}} 56 45 57 To set 46 To setup Trac environment for `mod_fcgid` it is necessary to use 58 47 `DefaultInitEnv` directive. It cannot be used in `Directory` or 59 48 `Location` context, so if you need to support multiple projects, try … … 64 53 }}} 65 54 66 === alternative environment setup===67 A better method to specify path to Trac environment i sto embed the path55 ==== alternative environment setup ==== 56 A better method to specify path to Trac environment it to embed the path 68 57 into `trac.fcgi` script itself. That doesn't require configuration of server 69 58 environment variables, works for both FastCgi modules … … 104 93 105 94 After doing this, we will just have to create a new rule managed by the SCGI handler to access Trac. It can be created in a new virtual server, trac.example.net for instance, and will only need two rules. The '''default''' one will use the SCGI handler associated to the previously created information source. 106 The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''$TRAC_LOCAL/htdocs/'' (where $TRAC_LOCAL is a directory defined by the user or the system administrator to place local trac resources). 107 108 Note:\\ 109 If the tracd process fails to start up, and cherokee displays a 503 error page, you might be missing the [http://trac.saddi.com/flup python-flup] package.\\ 110 Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with: 111 {{{ 112 sudo apt-get install python-flup 113 }}} 114 95 The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/chrome/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''/usr/share/trac/htdocs/'' 115 96 116 97 == Simple Lighttpd Configuration == … … 142 123 using `bin-environment` (as in the section above on Apache configuration). 143 124 144 Note that lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example (see [trac:#2418]). This should be fixed since lighttpd 1.4.23, and you may need to add `"fix-root-scriptname" => "enable"` as parameter of fastcgi.server.125 Note that lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example, see #Trac2418. This should be fixed since lighttpd 1.4.23, and you may need to add `"fix-root-scriptname" => "enable"` as parameter of fastcgi.server. 145 126 146 127 For using two projects with lighttpd add the following to your `lighttpd.conf`: … … 171 152 Note that the above will result in different processes in any event, even 172 153 if both are running from the same `trac.fcgi` script. 173 174 154 {{{ 175 155 #!div class=important 176 156 '''Note''' It's very important the order on which server.modules are loaded, if mod_auth is not loaded '''BEFORE''' mod_fastcgi, then the server will fail to authenticate the user. 177 157 }}} 178 179 158 For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules: 180 159 {{{ … … 224 203 server.modules += ("mod_alias") 225 204 226 # Set 205 # Setup an alias for the static resources 227 206 alias.url = ("/trac/chrome/common" => "/usr/share/trac/htdocs") 228 207 … … 290 269 For details about languages specification see [trac:TracFaq TracFaq] question 2.13. 291 270 292 Other important information like the [wiki:TracInstall#MappingStaticResources mapping static resources advices] are useful for non-fastcgi specific installation aspects. 293 ] 271 Other important information like [http://trac.lighttpd.net/trac/wiki/TracInstall this updated TracInstall page], [wiki:TracCgi#MappingStaticResources and this] are useful for non-fastcgi specific installation aspects. 272 273 If you use trac-0.9, read [http://lists.edgewall.com/archive/trac/2005-November/005311.html about small bug] 294 274 295 275 Relaunch lighttpd, and browse to `http://yourhost.example.org/trac` to access Trac. … … 297 277 Note about running lighttpd with reduced permissions: 298 278 299 If nothing else helps and trac.fcgi doesn't start with lighttpd settings `server.username = "www-data"`, `server.groupname = "www-data"`, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.279 If nothing else helps and trac.fcgi doesn't start with lighttpd settings `server.username = "www-data"`, `server.groupname = "www-data"`, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing. 300 280 301 281 … … 305 285 306 286 !LiteSpeed web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. !LiteSpeed can operate directly from an Apache config file and is targeted for business-critical environments. 287 288 === Setup === 307 289 308 290 1. Please make sure you have first have a working install of a Trac project. Test install with “tracd” first. … … 365 347 }}} 366 348 367 368 349 == Simple Nginx Configuration == 369 350 370 Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately. 371 372 1. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32 351 1. Nginx configuration snippet - confirmed to work on 0.6.32 373 352 {{{ 374 353 server { … … 389 368 if ($uri ~ ^/(.*)) { 390 369 set $path_info /$1; 391 }392 393 # it makes sense to serve static resources through Nginx394 location /chrome/ {395 alias /home/trac/instance/static/htdocs/;396 370 } 397 371 … … 422 396 fastcgi_param SERVER_PORT $server_port; 423 397 fastcgi_param SERVER_PROTOCOL $server_protocol; 424 fastcgi_param QUERY_STRING $query_string; 425 426 # For Nginx authentication to work - do not forget to comment these 427 # lines if not using Nginx for authentication 398 fastcgi_param QUERY_STRING $query_string; 399 400 # for authentication to work 428 401 fastcgi_param AUTH_USER $remote_user; 429 402 fastcgi_param REMOTE_USER $remote_user; 430 431 # for ip to work432 fastcgi_param REMOTE_ADDR $remote_addr;433 434 # For attchments to work435 fastcgi_param CONTENT_TYPE $content_type;436 fastcgi_param CONTENT_LENGTH $content_length;437 403 } 438 404 }