nginx-proxy / nginx-proxy/nginx-proxy
nginx-proxy with regular app
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
I am more looking into whether nginx-proxy suits my needs or not.
I currently have a python flask app (lets say at www.test.com) that spawns docker containers at incrementing port numbers eg (test.com:3001, test.com:3002, etc). I also allow the users to specify their own subdomain (user3001.test.com, user3002.test.com...). How would I go about keeping a python app (non dockerized, must be on port 80) alongside nginx-proxy (which will handle all the virtualhost stuff but still run on port 80)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no file, test, or entry point to change. Start by reading the nginx-proxy documentation and configuration guidance, then determine whether a non-containerized Flask app can share port 80 with nginx-proxy while Docker containers receive subdomains. Done means documenting a supported configuration or clearly stating that it is not supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, flask, nginx, python
- Domain
- devops, infrastructure, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100