On Fri, Oct 14, 2016 at 5:15 AM, Avraham Serour <tovm...@gmail.com> wrote:
> I will take a wild guess here and say that this is a modwsgi problem, it
> seems it will only load the django app after the first request.
Indeed, see this SO post for how to tell it to load your app
immediately on start up:
(EasyReader: Add "WSGIImportScript" directive)
> Honestly I suggest you to use nginx with uwsgi, the killer feature is that
> it is not apache, I ran with so many bumps with apache that I turned to
> nginx and never looked back.
> Also the config files are sane and will not drive you crazy.
Apache is an excellent webserver, particularly Apache 2.4. It has the
largest installed base and ecosystem of third party support and
packages, and can be configured to serve both the smallest and the
largest sites without any bothers. If you are already using apache and
happy with it (bar this issue), you will only waste time (and perhaps
get different issues) by switching to a different webserver.
To not get into a vim/emacs style situation, nginx/uwsgi is also
excellent; the choice of what webserver used is largely irrelevant to
how real django based sites (that actually do things) will perform.
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 post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.