Hi, I am not a particular evangelist of one or the other but since we use apache+mod_wsgi for several apps throughout the company, we obviously want to stick with one, easier for deployment and maintenance.
On Wednesday, October 16, 2013 5:17:35 PM UTC+2, Tom Evans wrote: > > On Wed, Oct 16, 2013 at 3:20 PM, <[email protected] <javascript:>> > wrote: > > Ouch! I should have read your post more carefully! If you don't have any > > other options than to use Apache, you could run it as proxy to gunicorn. > Or > > you could use Nginx instead of Apache... > > What, precisely, is wrong with Apache httpd/mod_wsgi as a hosting > solution? > > httpd can be as lean and efficient as nginx in memory usage if you > configure it so, doesn't abandon the httpd ecosystem, and can actually > host wsgi apps itself, rather than requiring yet another webserver in > to the mix. > > Especially so, I'd imagine, if that other webserver has, in your words > "some weird import errors which occured only when I was running the > project with `gunicorn_django" > > Cheers > > Tom > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/000f4297-bf65-4929-8bee-2d82b030cde2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
