Gunicorn VS NGINX Unit

Gunicorn mentions (31)

• Simplify Web App Development: Code Lite, Create Big!

  And Streamlit itself so far does not support Gunicorn, so its vertical scalability is limited. - Source: dev.to / 2 months ago

• Build a Vite 5 backend integration with Flask

  It's also worth mentioning that this Flask application is not production-ready. At the very least, you'll want to put an application server like Gunicorn in front of it (example in my repo). You'll also want to use a web server like NGINX to serve assets, or use a combination of WhiteNoise and a CDN to deliver assets. - Source: dev.to / 3 months ago

• Improving upon my OpenTelemetry Tracing demo

  Every time I started the Flask service, it showed a warning in red that it shouldn't be used in production. While it's unrelated to OpenTelemetry, and though nobody complained, I was not too fond of it. For this reason, I added a "real" HTTP server. I chose Gunicorn, for no other reason than because my knowledge of the Python ecosystem is still shallow. - Source: dev.to / 3 months ago

• Setting up Django in a Better Way in 5 Minutes and Understanding How It Works

  The static files are managed with whitenoise, Gunicorn is used for the WSGI server and Sentry is used for error monitoring and reporting in production. - Source: dev.to / 6 months ago

• Build a CI/CD pipeline for Flask apps using GitHub Actions

  Now, we can create the Procfile for Heroku. The Procfile contains the command that will be run once the application is deployed on Heroku. You can do this by creating a new file named Procfile and pasting the following command. We will be using Gunicorn to run the application instead of the default Flask server. - Source: dev.to / 7 months ago

NGINX Unit mentions (0)