Repository files navigation

This Docker image is now deprecated. Read about it below.

• python3.12,latest(Dockerfile)
• python3.11,(Dockerfile)
• python3.10(Dockerfile)

🚨 These tags are no longer supported or maintained, they are removed from the GitHub repository, but the last versions pushed might still be available in Docker Hub if anyone has been pulling them:

• python3.9
• python3.8
• python3.8-alpine
• python3.7
• python3.6
• python2.7

The last date tags for these versions are:

• • python3.9-2025-11-09
• python3.8-2024-10-28
• python3.8-alpine-2024-03-11
• python3.7-2024-10-28
• python3.6-2022-11-25
• python2.7-2022-11-25

Note: There aretags for each build date. If you need to "pin" the Docker image version you use, you can select one of those tags. E.g.tiangolo/uwsgi-nginx-flask:python3.7-2019-10-14.

Docker image withuWSGI andNginx forFlask web applications inPython running in a single container.

ThisDocker image allows you to createFlask web applications inPython that run withuWSGI andNginx in a single container.

The combination of uWSGI with Nginx is acommon way to deploy Python Flask web applications.

GitHub repo:https://github.com/tiangolo/uwsgi-nginx-flask-docker

Docker Hub image:https://hub.docker.com/r/tiangolo/uwsgi-nginx-flask/

You are probably usingKubernetes or similar tools. In that case, you probablydon't need this image (or any othersimilar base image). You are probably better offbuilding a Docker image from scratch.

If you have a cluster of machines withKubernetes, Docker Swarm Mode, Nomad, or other similar complex system to manage distributed containers on multiple machines, then you will probably want tohandle replication at thecluster level instead of using aprocess manager in each container that starts multipleworker processes, which is what this Docker image does.

In those cases (e.g. using Kubernetes) you would probably want to build aDocker image from scratch, installing your dependencies, and runninga single process instead of this image.

For example, usingGunicorn you could have a fileapp/gunicorn_conf.py with:

# Gunicorn config variablesloglevel="info"errorlog="-"# stderraccesslog="-"# stdoutworker_tmp_dir="/dev/shm"graceful_timeout=120timeout=120keepalive=5threads=3

And then you could have aDockerfile with:

FROM python:3.12WORKDIR /codeCOPY ./requirements.txt /code/requirements.txtRUN pip install --no-cache-dir --upgrade -r /code/requirements.txtCOPY ./app /code/appCMD ["gunicorn","--conf","app/gunicorn_conf.py","--bind","0.0.0.0:80","app.main:app"]

You can read more about these ideas in theFastAPI documentation about: FastAPI in Containers - Docker as the same ideas would apply to other web applications in containers.

uWSGI is now in maintenance mode, so it's probably better to migrate to a different tool.

Additionally, I haven't used this Docker image in years, so I don't have much bandwidth to keep it up to date. Most of my time is dedicated toFastAPI and friends.

You can probably still use this image as-is, while you migrate to a different tool, but I won't be adding (and maintaining) support for new versions of Python.

The rest of the README is preserved mainly for historical reasons.

You don't have to clone this repo.

You can use this image as a base image for other images.

Assuming you have a filerequirements.txt, you could have aDockerfile like this:

FROM tiangolo/uwsgi-nginx-flask:python3.12COPY ./requirements.txt /app/requirements.txtRUN pip install --no-cache-dir --upgrade -r /app/requirements.txtCOPY ./app /app

There are several image tags available but for new projects you should use the latest version available.

This Docker image is based ontiangolo/uwsgi-nginx. That Docker image has uWSGI and Nginx installed in the same container and was made to be the base of this image.

• Go to your project directory
• Create aDockerfile with:

FROM tiangolo/uwsgi-nginx-flask:python3.12COPY ./app /app

• Create anapp directory and enter in it
• Create amain.py file (it should be named like that and should be in yourapp directory) with:

fromflaskimportFlaskapp=Flask(__name__)@app.route("/")defhello():return"Hello World from Flask"if__name__=="__main__":# Only for debugging while developingapp.run(host='0.0.0.0',debug=True,port=80)

the main application object should be namedapp (in the code) as in this example.

Note: The section with themain() function is for debugging purposes. To learn more, read theAdvanced instructions below.

• You should now have a directory structure like:

.├── app│   └── main.py└── Dockerfile

• Go to the project directory (in where yourDockerfile is, containing yourapp directory)
• Build your Flask image:

docker build -t myimage.

• Run a container based on your image:

docker run -d --name mycontainer -p 80:80 myimage

...and you have an optimized Flask server in a Docker container.

You should be able to check it in your Docker container's URL, for example:http://192.168.99.100 orhttp://127.0.0.1

If you are building modern frontend applications (e.g.Vue,React,Angular) you would most probably be compiling a modern version of JavaScript (ES2015, TypeScript, etc) to a less modern, more compatible version.

If you want to serve your (compiled) frontend code by the same backend (Flask) Docker container, you would have to copy the code to the container after compiling it.

That means that you would need to have all the frontend tools installed on the building machine (it might be your computer, a remote server, etc).

That also means that you would have to, somehow, always remember to compile the frontend code right before building the Docker image.

And it might also mean that you could then have to add your compiled frontend code to yourgit repository (hopefully you are using Git already, orlearning how to usegit).

Adding your compiled code to Git is a very bad idea for several reasons, some of those are:

• You don't have a single, ultimate source of truth (the source code).
• The compiled code might be stale, even when your source code is new, which might make you spend a lot of time debugging.
• You might run into a lot of code conflicts when interacting with multiple team members with different Git branches, and spend a lot of time solving irrelevant code conflicts in the compiled code.
  • This might also ruin automatic branch merging in pull requests from other team members.

For these reasons, it is not recommended that you serve your frontend code from the same backend (Flask) Docker container.

There's a much better alternative to serving your frontend code from the same backend (Flask) Docker container.

You can have another Docker container with all the frontend tools installed (Node.js, etc) that:

• Takes your source frontend code.
• Compiles it and generates the final "distributable" frontend.
• Uses Docker "multi-stage builds" to copy that compiled code into a pure Nginx Docker image.
• The final frontend image only contains the compiled frontend code, directly from the source, but has the small size of an Nginx image, with all the performance from Nginx.

To learn the specifics of this process for the frontend building in Docker you can read:

• React in Docker with Nginx, built with multi-stage Docker builds, including testing
• Angular in Docker with Nginx, supporting configurations / environments, built with multi-stage Docker builds and testing with Chrome Headless

After having one backend (Flask) container and one frontend container, you need to serve both of them.

And you might want to serve them under the same domain, under a different path. For example, the backend (Flask) app at the path/api and the frontend at the "root" path/.

You can then useTraefik to handle that.

And it can also automatically generate HTTPS certificates for your application using Let's Encrypt. All for free, in a very easy setup.

In this scenario, you would have 3 Docker containers:

• Backend (Flask)
• Frontend (Vue.js, Angular, React or any other)
• Traefik (load balancer, HTTPS)

You should be able to follow the same instructions as in the "QuickStart" section above, with some minor modifications:

• Instead of putting your code in theapp/ directory, put it in a directoryapp/app/.
• Add an empty file__init__.py inside of thatapp/app/ directory.
• Add a fileuwsgi.ini inside yourapp/ directory (that is copied to/app/uwsgi.ini inside the container).
• In youruwsgi.ini file, add:

[uwsgi]module = app.maincallable = app

The explanation of theuwsgi.ini is as follows:

• The module in where my Python web app lives isapp.main. So, in the packageapp (/app/app), get themain module (main.py).
• The Flask web application is theapp object (app = Flask(__name__)).

Your file structure would look like:

.├── app│   ├── app│   │   ├── __init__.py│   │   ├── main.py│   └── uwsgi.ini└── Dockerfile

...instead of:

.├── app│   ├── main.py└── Dockerfile

If you are using static files in the same container, make sure theSTATIC_PATH environment variable is set accordingly, for example to change the default value of/app/static to/app/app/static you could add this line to yourDockerfile:

ENV STATIC_PATH /app/app/static

...after that, everything should work as expected. All the other instructions would apply normally.

• After adding all your modules you could end up with a file structure similar to (taken from the example project):

.├── app│   ├── app│   │   ├── api│   │   │   ├── api.py│   │   │   ├── endpoints│   │   │   │   ├── __init__.py│   │   │   │   └── user.py│   │   │   ├── __init__.py│   │   │   └── utils.py│   │   ├── core│   │   │   ├── app_setup.py│   │   │   ├── database.py│   │   │   └── __init__.py│   │   ├── __init__.py│   │   ├── main.py│   │   └── models│   │       ├── __init__.py│   │       └── user.py│   └── uwsgi.ini└── Dockerfile

• Make sure you followthe official docs while importing your modules:

• For example, if you are inapp/app/main.py and want to import the module inapp/app/core/app_setup.py you would write it like:

from .coreimportapp_setup

or

fromapp.coreimportapp_setup

• And if you are inapp/app/api/endpoints/user.py and you want to import theusers object fromapp/app/core/database.py you would write it like:

from ...core.databaseimportusers

or

fromapp.core.databaseimportusers

You can customize several things using environment variables.

Notice: this technique is deprecated, as it can create several issues with modern frontend frameworks. For the details and better alternatives, read the section above.

Setting the environment variableSTATIC_INDEX to be1 you can configure Nginx to serve the file in the URL/static/index.html when requested for/.

That would improve speed as it would not involve uWSGI nor Python. Nginx would serve the file directly. To learn more follow the section above "QuickStart for SPAs".

For example, to enable it, you could add this to yourDockerfile:

ENV STATIC_INDEX 1

By default, the image starts with 2 uWSGI processes running. When the server is experiencing a high load, it creates up to 16 uWSGI processes to handle it on demand.

If you need to configure these numbers you can use environment variables.

The starting number of uWSGI processes is controlled by the variableUWSGI_CHEAPER, by default set to2.

The maximum number of uWSGI processes is controlled by the variableUWSGI_PROCESSES, by default set to16.

Have in mind thatUWSGI_CHEAPER must be lower thanUWSGI_PROCESSES.

So, if, for example, you need to start with 4 processes and grow to a maximum of 64, yourDockerfile could look like:

FROM tiangolo/uwsgi-nginx-flask:python3.12ENV UWSGI_CHEAPER 4ENV UWSGI_PROCESSES 64COPY ./app /app

You can set a custom maximum upload file size using an environment variableNGINX_MAX_UPLOAD, by default it has a value of0, that allows unlimited upload file sizes. This differs from Nginx's default value of 1 MB. It's configured this way because that's the simplest experience an inexperienced developer in Nginx would expect.

For example, to have a maximum upload file size of 1 MB (Nginx's default) add a line in yourDockerfile with:

ENV NGINX_MAX_UPLOAD 1m

By default, the container made from this image will listen on port 80.

To change this behavior, set theLISTEN_PORT environment variable. You might also need to create the respectiveEXPOSE Docker instruction.

You can do that in yourDockerfile, it would look something like:

FROM tiangolo/uwsgi-nginx-flask:python3.12ENV LISTEN_PORT 8080EXPOSE 8080COPY ./app /app

There is a default file in/app/uwsgi.ini with app specific configurations (on top of the globaluwsgi configurations).

It only contains:

[uwsgi]module = maincallable = app

• module = main refers to the filemain.py.
• callable = app refers to theFlask "application", in the variableapp.

You can customizeuwsgi by replacing that file with your own, including all your configurations.

For example, to extend the default one above and enable threads, you could have a file:

[uwsgi]module = maincallable = appenable-threads = true

You can override where the image should look for the appuwsgi.ini file using the environment variableUWSGI_INI.

With that you could change the default directory for your app from/app to something else, like/application.

For example, to make the image use the file in/application/uwsgi.ini, you could add this to yourDockerfile:

ENV UWSGI_INI /application/uwsgi.iniCOPY ./application /applicationWORKDIR /application

Note: theWORKDIR is important, otherwise uWSGI will try to run the app in/app.

Note: you would also have to configure thestatic files path, read below.

You can make Nginx use a custom directory path with the files to serve directly (without having uWSGI involved) with the environment variableSTATIC_PATH.

For example, to make Nginx serve the static content using the files in/app/custom_static/ you could add this to yourDockerfile:

ENV STATIC_PATH /app/custom_static

Then, when the browser asked for a file in, for example,http://example.com/static/index.html, Nginx would answer directly using a file in the path/app/custom_static/index.html.

Note: you would also have to configure Flask to use that as itsstatic directory.

As another example, if you needed to put your application code in a different directory, you could configure Nginx to serve those static files from that different directory.

If you needed to have your static files in/application/static/ you could add this to yourDockerfile:

ENV STATIC_PATH /application/static

You can also make Nginx serve the static files in a different URL, for that, you can use the environment variableSTATIC_URL.

For example, if you wanted to change the URL/static to/content you could add this to yourDockerfile:

ENV STATIC_URL /content

Then, when the browser asked for a file in, for example,http://example.com/content/index.html, Nginx would answer directly using a file in the path/app/static/index.html.

If you need to run anything before starting the app, you can add a fileprestart.sh to the directory/app. The image will automatically detect and run it before starting everything.

For example, if you want to add Alembic SQL migrations (with SQLAlchemy), you could create a./app/prestart.sh file in your code directory (that will be copied by yourDockerfile) with:

#! /usr/bin/env bash# Let the DB startsleep 10;# Run migrationsalembic upgrade head

and it would wait 10 seconds to give the database some time to start and then run thatalembic command.

If you need to run a Python script before starting the app, you could make the/app/prestart.sh file run your Python script, with something like:

#! /usr/bin/env bash# Run custom Python script before startingpython /app/my_custom_prestart_script.py

Note: The image usessource to run the script, so for example, environment variables would persist. If you don't understand the previous sentence, you probably don't need it.

By default, Nginx will start one "worker process".

If you want to set a different number of Nginx worker processes you can use the environment variableNGINX_WORKER_PROCESSES.

You can use a specific single number, e.g.:

ENV NGINX_WORKER_PROCESSES 2

or you can set it to the keywordauto and it will try to auto-detect the number of CPUs available and use that for the number of workers.

For example, usingauto, your Dockerfile could look like:

FROM tiangolo/uwsgi-nginx-flask:python3.12ENV NGINX_WORKER_PROCESSES autoCOPY ./app /app

By default, Nginx will start with a maximum limit of 1024 connections per worker.

If you want to set a different number you can use the environment variableNGINX_WORKER_CONNECTIONS, e.g:

ENV NGINX_WORKER_CONNECTIONS 2048

It cannot exceed the current limit on the maximum number of open files. See how to configure it in the next section.

The number connections per Nginx worker cannot exceed the limit on the maximum number of open files.

You can change the limit of open files with the environment variableNGINX_WORKER_OPEN_FILES, e.g.:

ENV NGINX_WORKER_OPEN_FILES 2048

If you need to configure Nginx further, you can add*.conf files to/etc/nginx/conf.d/ in yourDockerfile.

Just have in mind that the default configurations are created during startup in a file at/etc/nginx/conf.d/nginx.conf and/etc/nginx/conf.d/upload.conf. So you shouldn't overwrite them. You should name your*.conf file with something different thannginx.conf orupload.conf, for example:custom.conf.

Note: if you are customizing Nginx, maybe copying configurations from a blog or a StackOverflow answer, have in mind that you probably need to use theconfigurations specific to uWSGI, instead of those for other modules, like for example,ngx_http_fastcgi_module.

If you need to configure Nginx even further, completely overriding the defaults, you can add a custom Nginx configuration to/app/nginx.conf.

It will be copied to/etc/nginx/nginx.conf and used instead of the generated one.

Have in mind that, in that case, this image won't generate any of the Nginx configurations, it will only copy and use your configuration file.

That means that all the environment variables described above that are specific to Nginx won't be used.

It also means that it won't use additional configurations from files in/etc/nginx/conf.d/*.conf, unless you explicitly have a section in your custom file/app/nginx.conf with:

include /etc/nginx/conf.d/*.conf;

If you want to add a custom/app/nginx.conf file but don't know where to start from, you can usethenginx.conf used for the tests and customize it or modify it further.

The combination of uWSGI with Nginx is acommon way to deploy Python Flask web applications.

Roughly:

• Nginx is a web server, it takes care of the HTTP connections and also can serve static files directly and more efficiently.

• uWSGI is an application server, that's what runs your Python code and it talks with Nginx.

• Your Python code has the actualFlask web application, and is run by uWSGI.

The imagetiangolo/uwsgi-nginx takes advantage of already existing slim and optimized Docker images (based on Debian asrecommended by Docker) and implements several of Docker's best practices.

It uses the official Python Docker image, installs uWSGI and on top of that (with the least amount of modifications) adds the official Nginx image.

And it controls all these processes with Supervisord.

The image (and tags) created by this repo is based on the imagetiangolo/uwsgi-nginx. This image adds Flask and sensible defaults on top of it.

If you follow the instructions and keep the root directory/app in your container, with a file namedmain.py and a Flask object namedapp in it, it should "just work".

There's already auwsgi.ini file in the/app directory with the uWSGI configurations for it to "just work". And all the other required parameters are in anotheruwsgi.ini file in the image, inside/etc/uwsgi/.

If you need to change the main file name or the main Flask object, you would have to provide your ownuwsgi.ini file. You may use the one in this repo as a template to start with (and you only would have to change the 2 corresponding lines).

You can have a/app/static directory and those files will be efficiently served by Nginx directly (without going through your Flask code or even uWSGI), it's already configured for you. But you can configure it further using environment variables (read above).

Supervisord takes care of running uWSGI with theuwsgi.ini file in/app file (including also the file in/etc/uwsgi/uwsgi.ini) and starting Nginx.

There's the rule of thumb that you should have "one process per container".

That helps, for example, isolating an app and its database in different containers.

But if you want to have a "micro-services" approach you may want tohave more than one process in one container if they are all related to the same "service", and you may want to include your Flask code, uWSGI and Nginx in the same container (and maybe run another container with your database).

That's the approach taken in this image.

This image (and tags) have some default files, so if you run it by itself (not as the base image of your own project) you will see a default "Hello World" web app.

When you build aDockerfile with aCOPY ./app /app you replace those default files with your app code.

The main default file is only in/app/main.py. And in the case of the tags with-index, also in/app/static/index.html.

But those files render a "(default)" text in the served web page, so that you can check if you are seeing the default code or your own code overriding the default.

Your app code should be in the container's/app directory, it should have amain.py file and thatmain.py file should have a Flask objectapp.

If you follow the instructions above or use one of the downloadable example templates, you should be OK.

There is also a/app/uwsgi.ini file inside the images with the default parameters for uWSGI.

The downloadable examples include a copy of the sameuwsgi.ini file for debugging purposes. To learn more, read the "Advanced development instructions" below.

While developing, you might want to make your code directory a volume in your Docker container.

With that you would have your files (temporarily) updated every time you modify them, without needing to build your container again.

To do this, you can use the commandpwd (print working directory) inside yourdocker run and the flag-v for volumes.

With that you could map your./app directory to your container's/app directory.

But first, as you will be completely replacing the directory/app in your container (and all of its contents) you will need to have auwsgi.ini file in your./app directory with:

[uwsgi]module = maincallable = app

and then you can do the Docker volume mapping.

Note: Auwsgi.ini file is included in the downloadable examples.

• To try it, go to your project directory (the one with yourDockerfile and your./app directory)
• Make sure you have auwsgi.ini file in your./app directory
• Build your Docker image:

docker build -t myimage.

• Run a container based on your image, mapping your code directory (./app) to your container's/app directory:

docker run -d --name mycontainer -p 80:80 -v$(pwd)/app:/app myimage

If you go to your Docker container URL you should see your app, and you should be able to modify files in./app/static/ and see those changes reflected in your browser just by reloading.

...but, as uWSGI loads your whole Python Flask web application once it starts, you won't be able to edit your Python Flask code and see the changes reflected.

To be able to (temporarily) debug your Python Flask code live, you can run your container overriding the default command (that starts Supervisord which in turn starts uWSGI and Nginx) and run your application directly withpython, in debug mode, using theflask command with its environment variables.

So, with all the modifications above and making your app run directly withflask, the final Docker command would be:

docker run -d --name mycontainer -p 80:80 -v$(pwd)/app:/app -e FLASK_APP=main.py -e FLASK_DEBUG=1 myimage flask run --host=0.0.0.0 --port=80

Or in the case of a package project, you would setFLASK_APP=main/main.py:

docker run -d --name mycontainer -p 80:80 -v$(pwd)/app:/app -e FLASK_APP=main/main.py -e FLASK_DEBUG=1 myimage flask run --host=0.0.0.0 --port=80

Now you can edit your Flask code in your local machine and once you refresh your browser, you will see the changes live.

Remember that you should use this only for debugging and development, for deployment in production you shouldn't mount volumes and you should let Supervisord start and let it start uWSGI and Nginx (which is what happens by default).

An alternative for these last steps to work when you don't have a package, but just a flat structure with single files (modules), your Python Flask code could have that section with:

if__name__=="__main__":# Only for debugging while developingapp.run(host='0.0.0.0',debug=True,port=80)

...and you could run it withpython main.py. But that will only work when you are not using a package structure and don't plan to do it later. In that specific case, if you didn't add the code block above, your app would only listen tolocalhost (inside the container), in another port (5000) and not in debug mode.

Also, if you want to do the same live debugging using the environment variableSTATIC_INDEX=1 (to serve/app/static/index.html directly when requested for/) your Nginx won't serve it directly as it won't be running (only your Python Flask app in debug mode will be running).

fromflaskimportFlask,send_file

and

@app.route('/')defroute_root():index_path=os.path.join(app.static_folder,'index.html')returnsend_file(index_path)

...that makes sure your app also serves the/app/static/index.html file when requested for/. Or if you are using a package structure, the/app/main/static/index.html file.

And if you are using a SPA framework, to allow it to handle the URLs in the browser, your Python Flask code should have the section with:

# Everything not declared before (not a Flask route / API endpoint)...@app.route('/<path:path>')defroute_frontend(path):# ...could be a static file needed by the front end that# doesn't use the `static` path (like in `<script src="bundle.js">`)file_path=os.path.join(app.static_folder,path)ifos.path.isfile(file_path):returnsend_file(file_path)# ...or should be handled by the SPA's "router" in front endelse:index_path=os.path.join(app.static_folder,'index.html')returnsend_file(index_path)

...that makes Flask send all the CSS, JavaScript and image files when requested in the root (/) URL but also makes sure that your frontend SPA handles all the other URLs that are not defined in your Flask app.

That's how it is written in the tutorial above and is included in the downloadable examples.

If you follow the instructions above, it's probable that at some point, you will write code that will break your Flask debugging server and it will crash.

And since the only process running was your debugging server, that now is stopped, your container will stop.

Then you will have to start your container again after fixing your code and you won't see very easily what is the error that is crashing your server.

So, while developing, you could do the following (that's what I normally do, although I do it with Docker Compose, as in the example projects):

• Make your container run and keep it alive in an infinite loop (without running any server):

docker run -d --name mycontainer -p 80:80 -v$(pwd)/app:/app -e FLASK_APP=main.py -e FLASK_DEBUG=1 myimage bash -c"while true ; do sleep 10 ; done"

• Or, if your project is a package, setFLASK_APP=main/main.py:

docker run -d --name mycontainer -p 80:80 -v$(pwd)/app:/app -e FLASK_APP=main/main.py -e FLASK_DEBUG=1 myimage bash -c"while true ; do sleep 10 ; done"

• Connect to your container with a new interactive session:

dockerexec -it mycontainer bash

You will now be inside your container in the/app directory.

• Now, from inside the container, run your Flask debugging server:

flask run --host=0.0.0.0 --port=80

You will see your Flask debugging server start, you will see how it sends responses to every request, you will see the errors thrown when you break your code, and how they stop your server, and you will be able to re-start it very fast, by just running the command above again.

All the image tags, configurations, environment variables and application options are tested.

• ✨ Add Python 3.12. PR#386 by@tiangolo.

• ⬆ Bump flask from 3.1.1 to 3.1.2. PR#397 by@dependabot[bot].
• Bump flask from 3.1.0 to 3.1.1 in /docker-images. PR#393 by@dependabot[bot].
• ⬆ Bump flask from 2.2.5 to 3.1.0. PR#391 by@dependabot[bot].
• 🔥 Drop support for Python 3.7 and 3.8. PR#388 by@tiangolo.

• 📝 Add note about historical README. PR#403 by@tiangolo.
• 📝 Add deprecation note. PR#402 by@tiangolo.

• 👷 Upgrade actions/checkout from v5 to v6. PR#407 by@tiangolo.
• 👷 Upgradelatest-changes GitHub Action and pinactions/checkout@v5. PR#406 by@tiangolo.
• 🔥 Drop support for Python 3.9. PR#401 by@tiangolo.
• ⬆ Bump tiangolo/issue-manager from 0.5.1 to 0.6.0. PR#400 by@dependabot[bot].
• ⬆ Bump actions/labeler from 5 to 6. PR#399 by@dependabot[bot].
• ⬆ Bump actions/setup-python from 5 to 6. PR#398 by@dependabot[bot].
• ⬆ Bump actions/checkout from 4 to 5. PR#396 by@dependabot[bot].
• ⬆ Bump tiangolo/latest-changes from 0.3.2 to 0.4.0. PR#395 by@dependabot[bot].
• 👷 Add CI Labeler. PR#392 by@tiangolo.
• ⬆ Bump tiangolo/latest-changes from 0.3.1 to 0.3.2. PR#390 by@dependabot[bot].
• 🔥 Remove old unused files. PR#389 by@tiangolo.
• ⬆ Bump tiangolo/issue-manager from 0.5.0 to 0.5.1. PR#387 by@dependabot[bot].
• 👷 Updateissue-manager.yml. PR#385 by@tiangolo.
• 👷 Updatelatest-changes GitHub Action. PR#360 by@tiangolo.
• ⬆ Bump docker/build-push-action from 5 to 6. PR#359 by@dependabot[bot].
• ⬆ Bump docker/login-action from 1 to 3. PR#352 by@dependabot[bot].
• ⬆ Bump docker/setup-buildx-action from 1 to 3. PR#351 by@dependabot[bot].
• ⬆ Bump docker/build-push-action from 2 to 5. PR#350 by@dependabot[bot].
• ⬆ Bump actions/setup-python from 4 to 5. PR#349 by@dependabot[bot].
• 👷 Update issue-manager.yml GitHub Action permissions. PR#357 by@tiangolo.
• 🔧 Add GitHub templates for discussions and issues, and security policy. PR#354 by@alejsdev.
• 🔧 Updatelatest-changes.yml. PR#348 by@alejsdev.

• ✨ Add support for multiarch builds, including ARM (e.g. Mac M1). PR#347 by@tiangolo.

• 🔥 Remove Alpine support. PR#345 by@tiangolo.

• ✏️ Fix typo in README. PR#316 by@cclauss.
• 📝 Update test badge inREADME.md. PR#346 by@alejsdev.

• ⬆️ Bump flask from 2.2.3 to 2.2.5 in /docker-images. PR#327 by@dependabot[bot].
• ⬆️ Bump flask from 2.2.2 to 2.2.3. PR#321 by@dependabot[bot].

• 👷 Update latest-changes GitHub Action. PR#335 by@tiangolo.
• ⬆️ Update mypy requirement from ^0.991 to ^1.1. PR#322 by@dependabot[bot].
• ⬆️ Update black requirement from ^22.10 to ^23.1. PR#319 by@dependabot[bot].
• ⬆️ Bump actions/setup-python from 4.3.0 to 4.5.0. PR#318 by@dependabot[bot].
• 👷 Update token for latest changes. PR#326 by@tiangolo.
• 👷 Add GitHub Action for Docker Hub description. PR#313 by@tiangolo.
• ⬆ Bump actions/setup-python from 4.7.1 to 5.0.0. PR#338 by@dependabot[bot].
• ⬆ Bump peter-evans/dockerhub-description from 3 to 4. PR#341 by@dependabot[bot].
• ⬆ Bump tiangolo/issue-manager from 0.4.0 to 0.5.0. PR#342 by@dependabot[bot].
• 👷 Update dependabot. PR#336 by@tiangolo.
• ⬆️ Bump actions/setup-python from 4.5.0 to 4.7.1. PR#333 by@dependabot[bot].
• ⬆️ Bump actions/checkout from 3 to 4. PR#332 by@dependabot[bot].

Highlights of this release:

• Support for Python 3.10, 3.11, and 3.9.
• Deprecation of Python 3.6 and 2.7.
  • The last Python 3.6 and 2.7 images are available in Docker Hub, but they won't be updated or maintained anymore.
  • The last images with a date tag arepython3.6-2022-11-25 andpython2.7-2022-11-25.
• Upgraded versions of all the dependencies.
• Small improvements and fixes.

• ✨ Add support for Python 3.11. PR#312 by@tiangolo.
• ✨ Add support for Python 3.10. PR#253 by@tiangolo.
• ♻ Add pip flag --no-cache-dir to reduce disk size used. PR#242 by@tiangolo.
• ✨ Add Python 3.9 image. PR#232 by@tiangolo.

• 🔥 Deprecate and remove Python 3.6. PR#304 by@tiangolo.
• 🔥 Remove support for Python 2.7. PR#246 by@tiangolo.

• ⬆️ Bump flask from 2.0.1 to 2.2.2 in /docker-images. PR#296 by@dependabot[bot].
• ⬆️ Upgrade Flask to the latest version to support Python 3.6. PR#301 by@tiangolo.
• ⬆️ Upgrade Nginx and Alpine (in the base images). PR#283 by@tiangolo.

• ✏️ Fix typo: otherwhise -> otherwise in README. PR#211 by@timgates42.
• 📝 Add note to discourage Alpine with Python. PR#247 by@tiangolo.
• 📝 Add Kubernetes warning, when to use this image. PR#245 by@tiangolo.
• ✏️ ️Fix typo duplicate "Note" in Readme. PR#243 by@tiangolo.
• Fix example for Python 3.8. PR#186 by@ericboucher.

• ⬆️ Update autoflake requirement from ^1.3.1 to ^2.0.0. PR#307 by@dependabot[bot].
• ⬆️ Update black requirement from ^20.8b1 to ^22.10. PR#308 by@dependabot[bot].
• ⬆️ Update docker requirement from ^5.0.3 to ^6.0.1. PR#309 by@dependabot[bot].
• ⬆️ Update mypy requirement from ^0.971 to ^0.991. PR#310 by@dependabot[bot].
• ⬆️ Upgrade CI OS. PR#311 by@tiangolo.
• 🔧 Update Dependabot config. PR#306 by@tiangolo.
• 🔥 Remove Travis backup file. PR#254 by@tiangolo.
• ⬆️ Bump tiangolo/issue-manager from 0.2.0 to 0.4.0. PR#234 by@dependabot[bot].
• 👷 Add scheduled CI. PR#303 by@tiangolo.
• 👷 Add alls-green GitHub Action. PR#302 by@tiangolo.
• ⬆️ Bump actions/setup-python from 4.2.0 to 4.3.0. PR#299 by@dependabot[bot].
• ⬆️ Update black requirement from ^19.10b0 to ^20.8b1. PR#236 by@dependabot[bot].
• ⬆️ Update docker requirement from ^4.2.0 to ^5.0.3. PR#250 by@dependabot[bot].
• ⬆️ Update isort requirement from ^4.3.21 to ^5.8.0. PR#237 by@dependabot[bot].
• ⬆️ Update pytest requirement from ^5.4.1 to ^7.0.1. PR#270 by@dependabot[bot].
• ⬆️ Bump actions/checkout from 2 to 3.1.0. PR#298 by@dependabot[bot].
• ⬆️ Update mypy requirement from ^0.770 to ^0.971. PR#292 by@dependabot[bot].
• ⬆️ Bump actions/setup-python from 1 to 4.2.0. PR#293 by@dependabot[bot].
• 👷 Run tests only on PRs or when pushing on master to avoid double CI. PR#284 by@tiangolo.
• 👷 Update Latest Changes GitHub Action. PR#241 by@tiangolo.
• 👷 Add Dependabot and external dependencies to get automated upgrade PRs. PR#233 by@tiangolo.
• 👷 Add GitHub Action latest-changes. PR#210 by@tiangolo.

• AddGitHub Sponsors button. PR#177.
• Add Python 3.8 and Alpine with Python 3.8. This also includes all the recent updates of the parent image, like:
  • Latest version of Nginx,1.17.10.
  • Latest version of Debian, Buster.
  • Latest version of Alpine,3.11.
  • PR#176.
• Remove support for Python 3.5. PR#175.
• Refactor build setup:
  • Move to GitHub actions.
  • Re-use and simplify code and configs.
  • Simplify and update tests.
  • Remove deprecated-index sufix tags.
  • PR#173.

• This is the last version to support:
  • Debian Stretch (before upgrading to Buster).
  • Python 3.5.
  • Alpine 3.7 and 3.8 (before upgrading to Alpine 3.11).
  • Alpine in older versions of Python, 2.7 and 3.6 (Before upgrading to Python 3.8).
  • Tags with-index (useENV STATIC_INDEX 1 instead).
  • If you need any of those, make sure to use a tag for the build date2020-05-04.

• Add note about static path in bigger projects. PR#150 by@reka169.
• Fix missing import in example. PR#141 by@Boyu1997.

• Refactor tests to use env vars and add image tags for each build date, liketiangolo/uwsgi-nginx-flask:python3.8-2019-10-14. PR#154.
• Upgrade Travis. PR#135.

• Move/start.sh and/app/prestart.sh functionality to parent image.PR #134.

2019-02-02:

• The Nginx configurations are generated dynamically from the entrypoint, instead of modifying pre-existing files.PR #50 in the parent imageuwsgi-nginx andPR #121.
• Support for a completely custom/app/nginx.conf file that overrides the generated one.PR #51 in the parent imageuwsgi-nginx andPR #122.

2019-01-01:

• Improved guide for single page applications.
• Links to project generators.

2018-12-29:

• Travis integration, images built and pushed by Travis.
• Fixes in parent image for Nginx.

2018-11-23:

• New Alpine 3.8 images for Python 2.7, Python 3.6 and (temporarily disabled) Python 3.7.

2018-09-22:

• New Python 3.7 images, based on standard Debian and Alpine Linux. All the documentation and project templates have been updated to use Python 3.7 by default. Thanks todesaintmartin inthis PR.

2018-06-22:

• You can now useNGINX_WORKER_CONNECTIONS to set the maximum number of Nginx worker connections andNGINX_WORKER_OPEN_FILES to set the maximum number of open files. Thanks toronlut inthis PR.

2018-06-22:

Improvements from parent image:

• Make uWSGI require an app to run, instead of going in "full dynamic mode" while there was an error. Supervisord doesn't terminate itself but tries to restart uWSGI and shows the errors. Usesneed-app as suggested byluckydonald inthis comment.

• Correctly handled graceful shutdown of uWSGI and Nginx. Thanks todesaintmartin inthis PR.

2018-02-04:

It's now possible to set the number of Nginx worker processes with the environment variableNGINX_WORKER_PROCESSES. Thanks tonaktinis inthis PR.

2018-01-14:

• There are now two Alpine based versions,python2.7-alpine3.7 andpython3.6-alpine3.7.

2017-12-10:

• Added support for/app/prestart.sh script to run arbitrary code before starting the app (for example, Alembic - SQLAlchemy migrations). Thedocumentation for the/app/prestart.sh is in the main README.
• /app is part of thePYTHONPATH environment variable. That allows global imports from several places, easier Alembic integration, etc.

2017-12-08: Now you can configure which port the container should listen on, using the environment variableLISTEN_PORT thanks totmshn inthis PR.

2017-09-10: Updated examples and sample project to work with SPAs even when structuring the app as a package (with subdirectories).

2017-09-02:

• Example project with aPython package structure and a section explaining how to use it and structure a Flask project like that.
• Also, the examples and documentation now use theflask run commands, that allows running a package application while developing more easily.

2017-08-10: Many changes:

• New official image tags:python3.6,python3.6-index,python.3.5,python3.5-index,python2.7 andpython2.7-index. All the other images are deprecated in favor is this ones.
• Python 3.6 is now the recommended default. Even the example projects for other versions were removed to discourage using older Python versions for new projects.
• Any of the older images that didn't have a Python version will show a deprecation warning and take some time to start. As soon the taglatest will point to Python 3.6 and the other tags will be removed.
• There were several improvements in the base imagetiangolo/uwsgi-nginx that improved this image too.
• By default, now there is no limit in the upload file size in Nginx. It can be configured in an environment variable.
• It's now possible to configure several things with environment variables:
  • Serveindex.html directly:STATIC_INDEX
  • Set the max upload file size:NGINX_MAX_UPLOAD
  • Set a customuwsgi.ini file (that allows using a custom directory different than/app):UWSGI_INI (using the ideas by @bercikr in #5 ).
  • Set a custom./static/ path:STATIC_PATH
  • Set a custom/static/ URL:STATIC_URL
• As all this configurations are available as environment variables, the choices are a lot more simple. Actually, any new project would just need to use aDockerfile with:

FROM tiangolo/uwsgi-nginx-flask:python3.6COPY ./app /app

and then customize with environment variables.

This project is licensed under the terms of the Apache license.