Mar-06-2017, 11:46 AM
I always start with the build web-server for Flask or Django when i build stuff local.
If i deploy i use Gunicorn with NGINX,this has a lot of power and are fairly simple to setup.
An other combo is that is used for Python is uWSGI with NGINX.
Eg Instagram use Gunicorn,they have a good approach to this:
The story is like this Python community did know that CGI was a bad approach,
so they went together to write an all Python solution WSGI and specified first in pep-333(2003) then later in pep-3333.
All Python web-framework is now build on WSGI.
Eg You see on Flask first page:
If i deploy i use Gunicorn with NGINX,this has a lot of power and are fairly simple to setup.
An other combo is that is used for Python is uWSGI with NGINX.
Eg Instagram use Gunicorn,they have a good approach to this:
Quote:
- Keep it very simple
- Don’t re-invent the wheel
- Go with proven and solid technologies when you can
Quote:it should support CGI although if that support is limited to scripts in python, that's ok.No it should not,CGI is dead or should be for all Python usages.
The story is like this Python community did know that CGI was a bad approach,
so they went together to write an all Python solution WSGI and specified first in pep-333(2003) then later in pep-3333.
All Python web-framework is now build on WSGI.
Eg You see on Flask first page:
Quote:100% WSGI 1.0 compliant