On Jul 9, 2009, at 6:16 PM, Jonathan Lundell wrote: > On Jul 8, 2009, at 11:44 PM, Yarko Tymciurak wrote: > >> On Thu, Jul 9, 2009 at 1:20 AM, Jonathan Lundell >> <jlund...@pobox.com> wrote: >> On Jul 8, 2009, at 10:01 PM, Yarko Tymciurak wrote: >> >>> you should be running this thru apache+mod_wsgi; >>> >>> with mod_wsgi you can just restart the mod_wsgi thread (and >>> thereby web2py) >> >> Sadly, no mod_wsgi on the box. I can ask. But I'm not sure how >> practical it is to run mod_wsgi without control over httpd.conf. >> >> You only need to set it up once - they should be able to help you >> with that (if they have mod_wsgi installed)... >> >> For starting, stopping, reloading web2py, read up on the WSGI >> reoload mechanism (mod_wsgi 2 or later). > > They do not. > > A question, though: I only need to do this for some light demo work, > so performance isn't an issue. The documentation implies that I can > run web2py via CGI, but it's not clear to me how to set that up. > What do I have to do?
OK, I tracked down a little more info. I'll give it a shot. I'm tentatively assuming that I sent all requests to cgihandler.py and that web2py'll sort things out from the request headers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
