On Apr 16, 11:17 pm, Graham Dumpleton <[email protected]> wrote: > For virtual environments read: > > http://code.google.com/p/modwsgi/wiki/VirtualEnvironments > > What you are doing is not sufficient.
As pylons now sets the egg cache, I didn't see why it was needed to reset it. As it stands, the documentation on the mod_wsgi wiki doesn't work. The suggested config from http://pylonsbook.com/en/1.1/deployment.html#setting-up-a-virtual-host worked as long as the system Python was the same version as the virtualenv. It did not work on a system where python had been upgraded, but the virtualenv had not been. Perhaps sys.path.insert would b > > Also read: > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Browser_Bas... > > You can still have DEBUG be true, but you must run a configuration > whereby all requests go to the same process. On UNIX boxes that means > using daemon mode and allowing the default of one process to be used. > Don't use 'processes=1' as that is a special case and still results in > wsgi.multitoprocess being true, just leave the processes option out > all together. I figured documenting issues people might... We'll just document things internally, sorry to have interrupted the list. -- 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.
