On Jan 13, 2:27 pm, Jorge Vargas <[email protected]> wrote:
> Hi,
>
> 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
> athttp://code.google.com/p/modwsgi/wiki/IntegrationWithPylonsfor a
> turbogears2 deployment. I also notice this is used
> athttp://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 athttp://code.google.com/p/modwsgi
> exclusively?
Hello,
The modwsgideploy is based on the same documentation you are referring
to. What I have tried to do with modwsgideploy is to create a default
set of configuration that will get the app running as soon as
possible. While using modwsgi on tg1 I've learned that every time the
settings are the same and the only thing that changes is configuration
location. With modwsgideploy, the only thing you need to change is
where you store your app, copy the apache config file to apache folder
and enable the app in apache. This should get you going in 10min.
After that if you have any recommendations feel free to share them as
long as they are not custom specific to your specific application.
Thanks,
Lucas
>
> 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?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
