NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Parse /etc/hosts to allow using synonyms for IP addresses
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
NPM seems to ignore the /etc/hosts file, so it's impossible to use a concise name for your proxy Hosts Forward Hostname / IP. That would be very helpful in a setup where the forward hosts are not docker containers, or on a different docker host.
Describe the solution you'd like
Please make NPM resolve addresses in the /etc/hosts file, so with the following addition to the Docker-Compose file, we could use synonyms for hosts IP addresses:
extra_hosts:
- "host1:10.0.0.1"
- "host2:10.0.0.2"
This adds hosts to the containers internal /etc/hosts file.
Best wishes
Adrian
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 tracing how the proxy host's “Forward Hostname / IP” value is handled and how names are resolved inside the Docker container. Use the /etc/hosts and Docker Compose extra_hosts examples as the acceptance case: aliases such as host1 and host2 should resolve to their configured IP addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, nginx, typescript
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100