The canonical way to run a Django server is to link it up to a WSGI (uWSGI)
or gunicorn, then run Apache or Nginx on top of that. These latter two
things are typically handled through systemd. Some people use Docker or
Supervisor, but that might be a lot for you to learn right now. Gunicorn &
Nginx
Antonin,
Uri is right that runserver is only suitable for development. It's also
worth looking at during development - log output includes system check
failures, new migration detection, and stack traces when bugs occur. I
normally have it in a terminal window.
If you definitely want to run it in
I think the server run by "python manage.py runserver" is just a debugging
server, it is not suitable for production. For production you run a web
server such as Nginx or Apache which you configure to execute Django.
אורי
u...@speedy.net
On Mon, Sep 7, 2020 at 4:37 PM Antonín Drdácký wrote:
> H
Hello there,
This question on StackOverflow is a workaround for stopping the server
https://stackoverflow.com/questions/27066366/django-development-server-how-to-stop-it-when-it-run-in-background
Basically I would like to run the server and stop it by a program, it is
hard, when the default way i
Week ending September 6, 2020
*Triaged:*
https://code.djangoproject.com/ticket/31965 - MySQL fast-delete
optimizations introduced in Django 3.1 don't properly deal with aggregation
and cause performance regression. (accepted)
https://code.djangoproject.com/ticket/31944 - Use addCleanup()
>
> I believe the technical term of this is "a mess".
>
Looks like it!
I can't think of any reason why this inconsistency would be desirable.
Adding more checks is normally fine since they can be disabled by users who
want/rely on the behaviour.
On Sun, 6 Sep 2020 at 13:54, Shai Berger wrote:
