On Tue, Jan 13, 2009 at 3:01 PM, Graham Dumpleton <[email protected]> wrote: > > 2009/1/14 Jorge Vargas <[email protected]>: >> >> I'm a newbie here. And I found out there is a set of paster create >> templates called modwsgideploy. I'm wondering if this is "official" >> recommended or should I stick with the instructions at >> http://code.google.com/p/modwsgi/wiki/IntegrationWithPylons for a >> turbogears2 deployment. I also notice this is used at >> http://turbogears.org/2.0/docs/main/Deployment/modwsgi+virtualenv.html >> >> in other words, does the mod_wsgi team fully supports this approch or >> should I stick with the stuff at http://code.google.com/p/modwsgi >> exclusively? > > I haven't tried modwsgideploy, however, of the the Python web > frameworks available TurboGears is one of a couple which seem to take > more active interest in ensuring that their framework works with > mod_wsgi and provide specific mechanisms to make it easier to setup > and get running on mod_wsgi. That and some of the people doing that > work occasionally post here with questions, but also to help others.
ok then I'll go test that out and report back. > > Thus, for TurboGears 2.0, have no problem with anything they > recommend, especially since I haven't created any specific > instructions on how to use TurboGears 2.0 with mod_wsgi, due to lack > of time, and are largely relying on Pylons instructions, which I know > to not strictly be complete. The extra bits are I believe incorporated > into the modwsgideploy template already. > well I got at least 2 sites to deploy using TG2 + mod_wsgi. So I'll see if I can enhance the TG2 docs and make sure it all works fine, then maybe you could dedicate some time to make sure everything works as expected, it's so much easier to review code than to write it. :) >> Also I'm interested in deploying 3 instances of the same app >> (test,staging,prod) which will be the best deployment strategy? I'm >> assuming using 1 venv per app and have them all configured at wsgi. is >> this possible? > > Separate virtual environments is a good start. Also though run each in > a separate mod_wsgi daemon process. That way they are isolated from > each other and no chance of interference across the sub interpreter > boundary via environment variables of C library level global data. > ok I'll be sure to do that. Thanks! > Graham > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
