Em Tuesday 05 February 2008 12:12:49 Mark Ramm escreveu: > > What is recommended: > > 1. A different turbogears project for each "business app" which > > would then require a different port. Requires a little config management > > to keep track of the ports, but separates them better, and allows > > independent restart. > > > > 2. Or a single project with a "subcontroller" for each business > > app. Provides a single "master node" and everything under that. In a > > small company (I'm the only Python programmer) this provides ease of > > tracking what's "out there". > > I would go the second route personally. You'll have less memory > consumption, cleaner URL structures, and easier deployment.
What I do is a mix of 1 and 2. Every "business app" is a different TG project, but all of them are imported in a master app using entry points. So, to add a new app it is just a matter of installing a new business app and restarting master app (if you don't code the logic to create links on your main entry page, then you'll have to change it as well ;-)). > But I would guess that there might be other things that push towards > the first option. You mention independent restarts, which is an > advantage and a disadvantage (you need ot monitor them all, and make > sure they are all up.) If you hadn't mentioned that traffic was not > an issue, that would be another thing to consider. Can't he have them as separate WSGI applications? If he is proxying to TG then he'll need different ports, but if he's using WSGI then Apache will start things by itself, right? -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
