github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

[PR #112] [CLOSED] nginx-wsgi-flask - docker compose #820

New Issue
Closed
opened 2026-03-07 21:24:30 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-07 21:24:30 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/112
Author: @GrantBirki
Created: 3/21/2021
Status: ❌ Closed

Base: master ← Head: nginx-wsgi-flask-compose

📝 Commits (9)

📊 Changes

10 files changed (+306 additions, -0 deletions)

View changed files

➕ nginx-wsgi-flask/README.md (+104 -0)
➕ nginx-wsgi-flask/docker-compose.yaml (+30 -0)
➕ nginx-wsgi-flask/flask/Dockerfile (+32 -0)
➕ nginx-wsgi-flask/flask/app.py (+27 -0)
➕ nginx-wsgi-flask/flask/requirements.txt (+2 -0)
➕ nginx-wsgi-flask/flask/wsgi.py (+5 -0)
➕ nginx-wsgi-flask/nginx/Dockerfile (+32 -0)
➕ nginx-wsgi-flask/nginx/default.conf (+29 -0)
➕ nginx-wsgi-flask/nginx/nginx.conf (+43 -0)
➕ nginx-wsgi-flask/nginx/start.sh (+2 -0)

📄 Description

nginx-wsgi-flask

About

Adding a simple and secure docker-compose sample for using NGINX + WSGI + Flask.

This sample demonstrates using a reverse proxy that points to a WSGI handler with a Flask backend. All images are based on Alpine, use nonroot Docker users, are validated by healthchecks, and are simple/easy to use.

Note

This is a new PR that I created to resolve merge conflicts. It is based off this pull request

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/112 **Author:** [@GrantBirki](https://github.com/GrantBirki) **Created:** 3/21/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `nginx-wsgi-flask-compose` --- ### 📝 Commits (9) - [`7cf1cf4`](https://github.com/docker/awesome-compose/commit/7cf1cf47890edb03ec0dd3cc221bfaebeed9f3af) init nginx-wsgi-flask - [`3a68d51`](https://github.com/docker/awesome-compose/commit/3a68d514d788cdef3e92e68408c823d1ee4ec9cd) changed container count from three to two - [`bb6f27f`](https://github.com/docker/awesome-compose/commit/bb6f27f123ea704685c73ba84fb0a7fd8c3f0957) update to nginx:1.19.7-alpine - [`d294c39`](https://github.com/docker/awesome-compose/commit/d294c393a55ffb8ecd7c17f3cd167ba549f180bc) init nginx-wsgi-flask - [`889436b`](https://github.com/docker/awesome-compose/commit/889436b6d5f37f89a577eae88e71b95026cf7122) changed container count from three to two - [`b3d7258`](https://github.com/docker/awesome-compose/commit/b3d7258e56aacaac6186a5fb89eade09e49a45ca) update to nginx:1.19.7-alpine - [`ce185e4`](https://github.com/docker/awesome-compose/commit/ce185e45436c5e0c25a48b3dacb7faffd9f2f571) Merge branch 'nginx-wsgi-flask-compose' of https://github.com/GrantBirki/awesome-compose into nginx-wsgi-flask-compose - [`26e381f`](https://github.com/docker/awesome-compose/commit/26e381f279f15d214d9dd2b3342a9684b5126ea2) removing tls block for simplicity - [`670a639`](https://github.com/docker/awesome-compose/commit/670a63974a3c98cce9681288dcfec81c4cf6da91) added line break ### 📊 Changes **10 files changed** (+306 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `nginx-wsgi-flask/README.md` (+104 -0) ➕ `nginx-wsgi-flask/docker-compose.yaml` (+30 -0) ➕ `nginx-wsgi-flask/flask/Dockerfile` (+32 -0) ➕ `nginx-wsgi-flask/flask/app.py` (+27 -0) ➕ `nginx-wsgi-flask/flask/requirements.txt` (+2 -0) ➕ `nginx-wsgi-flask/flask/wsgi.py` (+5 -0) ➕ `nginx-wsgi-flask/nginx/Dockerfile` (+32 -0) ➕ `nginx-wsgi-flask/nginx/default.conf` (+29 -0) ➕ `nginx-wsgi-flask/nginx/nginx.conf` (+43 -0) ➕ `nginx-wsgi-flask/nginx/start.sh` (+2 -0) </details> ### 📄 Description # nginx-wsgi-flask ## About Adding a simple and secure docker-compose sample for using NGINX + WSGI + Flask. This sample demonstrates using a reverse proxy that points to a WSGI handler with a Flask backend. All images are based on Alpine, use nonroot Docker users, are validated by healthchecks, and are simple/easy to use. ## Note This is a new PR that I created to resolve merge conflicts. It is based off this [pull request](https://github.com/docker/awesome-compose/pull/101) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-07 21:24:30 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#820
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?