NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Feature Request: Let locations assign Access Lists
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.
It is very common to use locations instead of hosts, for example, /owntracks instead of owntracks.example.com.
For these cases it would be great if we can assign access lists to locations as well. Because the access control for the locations may be different from the underlying host.
Describe the solution you'd like
Add this:
to here:
Describe alternatives you've considered
Currently I use the extended settings to paste the access control lines manually. But this is not elegant and very error prone. Especially when I change a list, it won't be updated for these cases.
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
No files or tests are named in the issue. Start by tracing the existing location and host access-list assignment flow, then compare how access-list changes are propagated. Done means a location can use its own access list and list changes are reflected without manually pasting extended settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100