Changes between Version 42 and Version 43 of TracFastCgi

Timestamp:

May 14, 2008, 11:17:05 AM (16 years ago)

Author:

screwdriver@…

Comment:

—

TracFastCgi

@@ -387 +387 @@
 {{{
 #!/usr/bin/env python
-
+import os
 sockaddr = '/home/trac/run/instance.sock'
+os.environ['TRAC_ENV'] = '/home/trac/instance'
 
 try:
@@ -394 +395 @@
      import trac.web._fcgi
 
-     fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, bindAddress = sockaddr)
+     fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, 
+          bindAddress = sockaddr, umask = 7)
      fcgiserv.run()
 
@@ -418 +420 @@
 
 {{{
-trac@trac.example ~ $ TRAC_ENV=/home/trac/instance ./trac-standalone-fcgi.py 
+trac@trac.example ~ $ ./trac-standalone-fcgi.py 
 }}}
 
 The above assumes that:
- * There is a user trac for running trac instances and keeping trac environments in its home directory.
+ * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory.
  * /home/trac/instance contains a trac environment
  * /home/trac/htpasswd contains authentication information
-
-You may have to chmod the unix socket file so that nginx can connect to it. Check this if you keep getting 502 errors.
-
-Unfortunately nginx does not support variable expansion in fastcgi_pass directive, thus it is not possible to serve multiple trac instances from one server block. 
+ * /home/trac/run is owned by the same group the nginx runs under
+  * and if your system is Linux the /home/trac/run has setgid bit set (chmod g+s run)
+  * and patch from ticket #7239 is applied, or you'll have to fix the socket file permissions every time
+
+Unfortunately nginx does not support variable expansion in fastcgi_pass directive. 
+Thus it is not possible to serve multiple trac instances from one server block. 
 
 If you worry enough about security, run trac instances under separate users.