On 5/29/07, Chris Shenton <[EMAIL PROTECTED]> wrote: > > I used mod_python about 6 months back to get Apache to proxy HTTPS to > my Pylons app; it wasn't easy. > > Now I'm trying again with current Pylons, paste and friends. But I'm > again having troubles getting it to work. > > The simplest apache config I've seen is this from > http://pythonpaste.org/module-paste.modpython.html > > SetHandler python-program > PythonHandler paste.modpython > PythonOption paste.ini /path/to/production.ini > > This doesn't fail but shows nothing and there is nothing logged. Any > ideas what might be wrong (config? permissions?) or how I could get it > to log what it's trying and failing? > > Other configs I've seen require downloading some modpython_wsgi.py > file and then hacking it a bit, but there seem to be multiple > different versions of this, and even more different Apache config > styles to use it. I've tried some and they fail, then indicate a > .core file might have been created but it isn't so I can't diagnose it > that way. > > So what's the current recommended way to front Pylons with mod_apache? > Or if there are better ways to run Pylons apps behind Apache, what are > your recommendations currently?
The current favorite way to run Pylons apps behind Apache is to proxy them and use Paster. It's exactly the sort of problems that you ran into that make some of us wary of mod_python. (Hi, Alec!) Best Regards, -jj -- http://jjinux.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
