Just go with mod_wsgi and virtual hosts for each application. PHP and mod_wsgi may clash given the two modus operandi for Apache. MPM or prefork Alternatively you could use NGINX with gunicorn
On Friday, August 23, 2013 6:50:49 PM UTC+2, Jon Dufresne wrote: > > Hi, > > I am getting ready to deploy my Django application. This application must > serve several independent parties. In the past, I've done this with > multiple instances of a PHP application on the server. Is this the right > approach in the Django world? > > My server is running Apache and MySQL. Each instance of the application > will have its own configuration and database. These instances will not > communicate with each other in any way. These instances are all (possibly) > different versions of the same application running in their own virtualenv. > > My instinct is to go with the Apache mod_wsgi approach. As Apache is > already running successfully on the server serving PHP an static files. > > Any advice or good resources on how to accomplish what I am doing? All the > documentation seems to be targeted at one server with one Django > application. > > Thanks, > Jon > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
