NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Allow Access List to be assigned for individual Custom Locations
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 seems only possible to assign Access Lists for the main domain, not for the custom locations.
So, I'm not able to restrict a specific subpath, while leaving others publicly available.
Describe the solution you'd like
It would be great to have the possibility of adding an access list per individual custom location.
Maybe include a dropdown like this:
Describe alternatives you've considered
I'm manually copying/pasting a snippet on each custom domain, and if something changes, I have to change everything manually once more.
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 custom locations and Access Lists are represented and assigned in the management interface and proxy configuration. The issue provides no file or test names, so follow those entry points through the frontend and backend; done means an individual custom location can select an Access List without affecting other locations or the main domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- backend, full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100