On 12/22/06, Ian Bicking <[EMAIL PROTECTED]> wrote:
Max Ischenko wrote: > I have a site with a few php modules and I plan to write new ones in > python (Pylons). > > How should I structure those modules? Should I have single Pylons app > that just handles it all? Several installations served through a single > FastCGI/WSGI pipe? I generally would do several applications (if you really have independent functions), and then run them in one process using egg:Paste#urlmap to map different paths to different processes. Functionality that applied to several applications can either use shared library code, or WSGI middleware that you apply above Paste#urlmap in the config file. If you need to avoid dependencies (e.g., maybe one application will require version 1.0 of some library, and another application version 1.1) then you'll need separate processes, and separate environments using something like workingenv or virtual-python.
It's always possible to just use Apache to proxy to multiple applications. I'm sure Ian's a whiz at this stuff, but that would be my approach. 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 -~----------~----~----~----~------~----~------~--~---
