how do you handle requests if you deploy django with uwsgi?
did you execute the django file when you started the deployment? (just like on the native run server, listening all the time)
or do you want to re-execute the file when the request comes in?
so what is the process of using apache,uwsgi to deploy like this? Do you rerun the django or flask file for each request? Still running all the time, listening to a port.
Thank you.
uwsgi is a runserver, independent of django that removes these snooping refreshes from runserver, which is relatively stable, and supervisor is not the same thing. Supervisor is a process daemon system, and you can also use supervisor to guard uwsgi
first of all, you have to understand that uwsgi is a Web server gateway interface (Python Web Server Gateway Interface, abbreviated to WSGI) is a simple and general interface between Web server and Web application program or framework defined for Python language. The WSGI area is divided into two parts: one is "server" or "gateway", and the other is "application" or "application framework".
how do you handle requests if you deploy django with uwsgi?
when processing a request, uwsgi provides django with environment information and a callback function (Callback Function). When django finishes processing the request, the result is passed back to uwsgi through the aforementioned callback function.
Previous: How to introduce rem.js File into angular
Next: Antd design table dynamically changes the rowSelection problem