Hi, Tom and rok! I didn't mean to start http server flame war, Apache obviously has it's upsides and we also use it. What I've proposed is a simple, albeit dirty, workaround to run non-forked Django 1.6 in production.
For Django devs to be able to address the root of the issue and solve it properly you will probably need to prepare a sample bare bones Django project that has the issue. On Wednesday, October 16, 2013 7:23:53 PM UTC+4, rok wrote: > > 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]> 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/f7a4398d-bb0d-4351-bf8f-2cf1481078cb%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
