Changes between Version 87 and Version 88 of TracFastCgi
- Timestamp:
- Aug 19, 2015, 1:59:00 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFastCgi
v87 v88 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. 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 7 8 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. … … 81 81 == Cherokee Configuration 82 82 83 The configuration of Cherokee with Trac is quite simple. You will only need to know that you can spawn Trac as an SCGI process.84 You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. 83 Configuring [http://cherokee-project.com/ Cherokee] with Trac is straightforward, if you spawn Trac as an SCGI process. You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. 84 85 85 First set up an information source in cherokee-admin with a local interpreter: 86 86 … … 96 96 97 97 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. 98 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).99 100 '''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/flup python-flup] package (#9903). Python-flup is a dependency which provides trac with SCGI capability. You can install it on Debian based systems with:98 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). 99 100 '''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/flup python-flup] package (#9903). Python-flup is a dependency which provides Trac with SCGI capability. You can install it on Debian based systems with: 101 101 {{{#!sh 102 102 sudo apt-get install python-flup … … 318 318 {{{ 319 319 URI: /trac/ <--- URI path to bind to python fcgi app we created 320 Fast CGI App: [VHost Level] MyTractFCGI <--- select the trac fcgi extapp we just created320 Fast CGI App: [VHost Level] MyTractFCGI <--- select the Trac fcgi extapp we just created 321 321 Realm: TracUserDB <--- only if (4) is set. select realm created in (4) 322 322 }}} … … 450 450 451 451 ---- 452 See also: 452 See also: TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
