On May 24, 9:13 pm, Philip Jenvey <[EMAIL PROTECTED]> wrote: > If these are in fact separate applications, you can make each one its > own Pylons app. Then you might also have a common package of code > shared between all three (this would be a separate egg). > > Then at deployment time you can combine them into one composite > application with Paste URL map, via the ini file: > > http://pythonpaste.org/deploy/#composite-applications
Philip, Thanks for the reply. I guess I am not familiar enough with Pylons to know exactly what you mean by "application." However, I don't think I intend for my modules to be applications in and of themselves. For example, I don't want to have to worry about defining DB connections, having decorator templates (i.e. the look that is shared across all pages), etc. per module. Rather, I would envision a module using the DB connection the application defined (even though it would have its own tables / database objects, etc.) and having generic template blocks that fit into the overall look of the site that is defined at the application level. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
