On Thu, Oct 30, 2008 at 4:14 PM, Håkan Waara <[EMAIL PROTECTED]> wrote:
> > Hi folks, > > I'm in the process of for the first time deploying a django site that > (unfortunately) needs to share its Apache with an existing PHP site. > > I've been reading a bunch about mod_wsgi and in many places there are > mentions that setting up apache with mpm-worker (basically > multithreaded mode) will not work if you're also hosting a PHP site on > the same Apache; Apache will crash, and the world will collapse... The problem is with PHP, not mod_wsgi. The PHP manual has this FAQ entry: "*Why shouldn't I use Apache2 with a threaded MPM in a production environment?"*<http://www.php.net/manual/en/faq.installation.php#faq.installation.apache2>. Because PHP has a high number of C extensions, which in turn use existing libraries, your success really depends on the php modules, the libraries they use, and how they were all compiled. If you need to run PHP and mod_wsgi together, the prefork mpm is best. mod_wsgi alone will will work safely in a threaded environment and any of the non-experimental mpms. -Naitik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
