I have two sites I want to convert to Pylons. Each site is just a collection of independent components which could conceivably be separate WSGI applications. But the sites handle authentication, logging, and sessions for the components. It's sometimes desirable to plug a component from one site into another, but this is not a high priority.
Pylons has a one-level structure. It doesn't really work to create a Pylons project inside another, and the config file would have to be at the site level anyway. So I'm looking for another way to squeeze a two-level structure out of it. I'm also not sure I want a large number of tiny Pylons applications to keep track of. On the other hand, I need "bundles" of controllers, views, models, lib modules, and static files -- and that's what a Pylons application is. And it could conceivably be nice to run a component individually for debugging. Paste can mount multiple applications at different subdirectories. But I need authentication at the top level, so that doesn't seem feasible. A Pylons controller can be any WSGI application. So I could invoke another Pylons application at that point, with its own routes and controllers. IF I can carry the current session and config down to it, and get the logging in my main log. How would I set this up? Make a dummy controller that calls make_app(full_stack=False) at the module level and then calls the app in .__call__? Is there another way that doesn't involve a stub controller? -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
