running #Gunicorn exposed to the internet is not recommended because it sucks at #slowloris DoS attack handling; instead they recommend using #nginx, and provide a recommended configuration, including Unix-domain sockets (#uds).
on 02023-02-01apparently running #Gunicorn from #systemd with socket activation, there's some special way Gunicorn gets the socket from systemd, so it doesn't need a --bind or -b option?
on 02023-02-01You can also bind #Gunicorn to Unix-domain sockets (#uds) for secure reverse proxying. Gunicorn does try to remove the socket before exiting, but of course if it gets killed or crashes this will fail. In manual testing, though, I don’t see the behavior reported in this answer where you need to manually remove the socket file to get it to restart.
on 02023-02-01"Gunicorn", Green Unicorn is a web server for deploying #Django and other WSGI Python web apps. It looks like it might actually be simpler than #uWSGI. “... for a typical Django project, invoking Gunicorn would look like: $ gunicorn myproject.wsgi”