NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Access Lists per Custom Location
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.
No
Describe the solution you'd like
When adding access list, for proxy host, it is added to site and custom locations (if exsiting). Ideally one would like to have access from anywhere to a host e.g. www.host.com, but have the ability to apply Access Lists to custom locations to restrict access to portals like www.host.com/admin
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 access lists are applied to proxy hosts and how existing custom locations are represented and generated. Confirm the desired behavior for a host-wide open policy with a restricted custom location such as /admin; done means access-list controls can be applied independently to each custom location without changing the other locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- backend-api-design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100