2008/9/30 Van Gale <[EMAIL PROTECTED]>: > > Can roundup (issue tracker) interface directly with mod_wsgi or is some > other piece like flup needed? I really don't want to run other > processes, preferring to control everything from my apache + mod_wsgi > conf files.
Google search for 'roundup WSGI' reveals: http://roundup.sourceforge.net/doc-1.0/installation.html#wsgi-handler The example in there is: from wsgiref.simple_server import make_server # obtain the WSGI request dispatcher from roundup.cgi.wsgi_handler import RequestDispatcher tracker_home = 'demo' app = RequestDispatcher(tracker_home) httpd = make_server('', 8917, app) httpd.serve_forever() For mod_wsgi, I believe you would drop the last two lines and just use: # obtain the WSGI request dispatcher from roundup.cgi.wsgi_handler import RequestDispatcher tracker_home = 'demo' app = RequestDispatcher(tracker_home) Google does though also show up: http://www.nabble.com/WSGI-handler-is-not-thread-safe-td17342792.html This suggests that RequestDispatcher instance is not thread safe and so you may not be able to use it in multithreaded worker MPM embedded mode, or multithreaded daemon process mode. Whether that post is correct or still valid I have no idea, you would need to ask roundup developers what the story is. Now, whether the code snippets above will work I don't know. It may still be necessary to configure Python egg cache location and remap sys.stdout if roundup logs there when it shouldn't. At least trying starting out with that example though. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
