Changes between Version 67 and Version 68 of TracSubversion

Timestamp:

Jan 24, 2009, 3:27:13 AM (15 years ago)

Author:

Graham.Dumpleton@…

Comment:

Restricted mode issues not specific to mod_wsgi embedded mode.

TracSubversion

@@ -169 +169 @@
 }}}
 
-However, this problem can also occur using mod_wsgi in non-daemon mode. Running mod_wsgi in daemon mode, with one daemon group for each trac instance seems to fix the problem.
-
-Example for setting up daemon process groups in httpd.conf: (see also: [http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide QuickConfigurationGuide at googleCode]
-
-{{{
-WSGIDaemonProcess projectone user=wwwrun group=root threads=15 python-eggs=/trac/projectOne/egg-cache
-WSGIScriptAlias /projects/projectOne /trac/projectOne/trac.wsgi
-
-<Directory /trac/projectOne/>
-   WSGIProcessGroup projectone
-</Directory>
-
-
-WSGIDaemonProcess projecttwo user=wwwrun group=root threads=15 python-eggs=/trac/projectTwo/egg-cache
-WSGIScriptAlias /projects/projectTwo /trac/projectTwo/trac.wsgi
-
-<Directory /trac/projectTwo/>
-   WSGIProcessGroup projecttwo
-</Directory>
-
-}}}
-
-
+This problem can also occur when using mod_wsgi for both embedded mode or daemon mode. As documented in [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac integrating Trac with mod_wsgi], the solution is the same as for mod_python. That is, force Trac insatnce to run in main Python interpreter instance. When using mod_wsgi this is done using:
+{{{
+WSGIApplicationGroup %{GLOBAL}
+}}}
 
 ==== `TypeError: argument number 0: a 'apr_pool_t *' is expected, 'instance(<libsvn.core.GenericSWIGWrapper instance at 0x...>)' is received` ====