nginx-proxy / nginx-proxy/nginx-proxy
Ability to set the NETWORK_ACCESS default to prevent accidental service exposure
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
We use nginx-proxy in our office, but only need a select few things to be exposed to external clients. It would be nice if we had an option to set the default NETWORK_ACCESS so that we can whitelist containers for external use, rather than having to blacklist everything else
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
Start by locating the existing NETWORK_ACCESS handling and how container exposure defaults are configured. Determine where a configurable default would be applied, then verify that explicitly whitelisted containers are exposed while other containers remain inaccessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100