Changes between Version 4 and Version 5 of TracFastCgi
- Timestamp:
- Sep 24, 2024, 8:59:24 AM (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFastCgi
v4 v5 4 4 [[PageOutline(2-5, Contents, floated)]] 5 5 6 [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 a much wider variety of web servers.7 8 Note that unlike mod_python, FastCGI supports [http ://httpd.apache.org/docs/suexec.html Apache SuEXEC], ie run with different permissions than the web server runs with. `mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect.6 [https://fastcgi-archives.github.io 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 a much wider variety of web servers. 7 8 Note that unlike mod_python, FastCGI supports [https://httpd.apache.org/docs/suexec.html Apache SuEXEC], ie run with different permissions than the web server runs with. `mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect. 9 9 10 10 '''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]. … … 27 27 <IfModule mod_fastcgi.c> 28 28 AddHandler fastcgi-script .fcgi 29 FastCgiIpcDir /var/lib/apache2/fastcgi 29 FastCgiIpcDir /var/lib/apache2/fastcgi 30 30 </IfModule> 31 31 LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so … … 48 48 You can also specify the `PYTHON_EGG_CACHE` environment variable using a second `-initial-env` directive: 49 49 {{{#!apache 50 FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac \ 50 FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac \ 51 51 -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache 52 52 }}} … … 68 68 === Alternative environment setup 69 69 70 A better method to specify the path to the Trac environment is to embed the path into `trac.fcgi` script itself. That doesn't require configuration of the server environment variables, works for both [trac:FastCgi] modules as well as for [http ://www.lighttpd.net/ lighttpd] and CGI:70 A better method to specify the path to the Trac environment is to embed the path into `trac.fcgi` script itself. That doesn't require configuration of the server environment variables, works for both [trac:FastCgi] modules as well as for [https://www.lighttpd.net/ lighttpd] and CGI: 71 71 {{{#!python 72 72 import os … … 106 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 107 108 '''Note:''' If the tracd process fails to start up, and Cherokee displays a 503 error page, you might be missing the [http ://trac.saddi.com/fluppython-flup] package ([trac:#9903]). Python-flup is a dependency which provides Trac with SCGI capability. You can install it on Debian based systems with:108 '''Note:''' If the tracd process fails to start up, and Cherokee displays a 503 error page, you might be missing the [https://www.saddi.com/software/flup/ python-flup] package ([trac:#9903]). Python-flup is a dependency which provides Trac with SCGI capability. You can install it on Debian based systems with: 109 109 {{{#!sh 110 110 sudo apt-get install python-flup … … 113 113 == Lighttpd Configuration 114 114 115 The FastCGI front-end was developed primarily for use with alternative webservers, such as [http ://www.lighttpd.net/ Lighttpd].115 The FastCGI front-end was developed primarily for use with alternative webservers, such as [https://www.lighttpd.net/ Lighttpd]. 116 116 117 117 Lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance environments. It has a very low memory footprint compared to other web servers and takes care of CPU load. … … 122 122 var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable 123 123 fastcgi.server = ("/trac" => 124 124 125 125 ("trac" => 126 126 ("socket" => "/tmp/trac-fastcgi.sock", … … 180 180 # Separated password files for each project 181 181 # See "Conditional Configuration" in 182 # http ://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/configuration.txt182 # https://redmine.lighttpd.net/projects/lighttpd/repository/entry/doc/configuration.txt?rev=lighttpd-1.4.28 183 183 184 184 $HTTP["url"] =~ "^/first/" { … … 190 190 191 191 # Enable auth on trac URLs, see 192 # http ://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/authentication.txt192 # https://redmine.lighttpd.net/projects/lighttpd/repository/entry/doc/authentication.txt?rev=lighttpd-1.4.28 193 193 194 194 auth.require = ("/first/login" => … … 292 292 == !LiteSpeed Configuration 293 293 294 The FastCGI front-end was developed primarily for use with alternative webservers, such as [http ://www.litespeedtech.com/ LiteSpeed].294 The FastCGI front-end was developed primarily for use with alternative webservers, such as [https://www.litespeedtech.com/ LiteSpeed]. 295 295 296 296 !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. … … 332 332 1. Modify `/fullpathto/mytracproject/conf/trac.ini`: 333 333 {{{ 334 #find/set base_ rul, url, and link variables334 #find/set base_url, url, and link variables 335 335 base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to 336 336 url = http://yourdomain.com/trac/ <--- link of project … … 341 341 == Nginx Configuration 342 342 343 [http ://nginx.org/en/ Nginx] is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.343 [https://nginx.org/en/ Nginx] is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately. 344 344 345 345 1. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32 … … 417 417 import trac.web._fcgi 418 418 419 fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, 419 fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, 420 420 bindAddress = sockaddr, umask = 7) 421 421 fcgiserv.run() … … 438 438 439 439 }}} 440 1. Reload nginx and launch trac.fcgi: 440 1. Reload nginx and launch trac.fcgi: 441 441 {{{#!sh 442 trac@trac.example ~ $ ./trac-standalone-fcgi.py 442 trac@trac.example ~ $ ./trac-standalone-fcgi.py 443 443 }}} 444 444 … … 451 451 * and patch from [trac:#7239] is applied, or you'll have to fix the socket file permissions every time 452 452 453 Unfortunately Nginx does not support variable expansion in fastcgi_pass directive. 454 Thus it is not possible to serve multiple Trac instances from one server block. 455 456 If you worry enough about security, run Trac instances under separate users. 453 Unfortunately Nginx does not support variable expansion in fastcgi_pass directive. 454 Thus it is not possible to serve multiple Trac instances from one server block. 455 456 If you worry enough about security, run Trac instances under separate users. 457 457 458 458 Another way to run Trac as a FCGI external application is offered in [trac:#6224].
