Are uWSGI and Nginx required to serve a Flask app?

Setting up Flask with uWSGI and Nginx is quite difficult, and even with buildout scripts it takes quite some time, and has to be recorded to instructions to be reproduced later.

If I don’t plan a big load on server (it’s hidden from public), does it make sense to run it without uWSGI? (Flask can listen to a port. Can Nginx just forward requests?)

  • Connection refused for Docker application on OSX
  • Flask Rest API based on docker - Graceful shutdown
  • Making REST calls to flask service running on different port
  • Using a PostgreSQL database with Docker and Flask, how does it work?
  • How to determine cause of slow requests in Flask?
  • Error connecting to RDS Postgreql DB from inside Docker container
  • Does it make sense to not use even Nginx, just running bare flask app on a port?

  • docker compose oci runtime error, executable file not found in $PATH
  • nginx and docker: route all requests from each service properly
  • Artifactory bad gateway error
  • Assigning vhosts to Docker ports
  • Docker-compose and custom packages
  • How can I use Kalabox with a WordPress Install that has a nested web root?
  • 2 Solutions collect form web for “Are uWSGI and Nginx required to serve a Flask app?”

    When you “run Flask” you are actually running Werkzeug’s development WSGI server, and passing your Flask app as the WSGI callable.

    The development server is not intended for use in production. It is not designed to be particularly efficient, stable, or secure.

    Replace the Werkzeug dev server with a production-ready WSGI server such as Gunicorn or uWSGI when moving to production, no matter where the app will be available.

    The answer is similar for “should I use a web server”. WSGI servers happen to have HTTP servers but they will not be as good as a dedicated production HTTP server (Nginx, Apache, etc.).

    Flask documents how to deploy in various ways. Many hosting providers also have documentation about deploying Python or Flask.

    Presumably you already have a Flask app object and routes set up, but if you create the app like this:

    import flask
    app = flask.Flask(__name__)

    then set up your @app.route()s, and then when you want to start the app:

    import gevent
    app_server = gevent.wsgi.WSGIServer((host, port), app)

    Then you can just run your application directly rather than having to tell gunicorn or uWSGI or anything else to run it for you.

    I had a case where I wanted the utility of flask to build a web application (a REST API service) and found the inability to compose flask with other non-flask, non-web-service elements a problem. I eventually found gevent.wsgi.WSGIServer and it was just what I needed. After the call to app_server.serve_forever(), you can call app_server.stop() when your application wants to exit.

    In my deployment, my application is listening on localhost: using flask and gevent, and then I have nginx reverse-proxying HTTPS requests on another port and forwarding them to my flask service on localhost.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.