nextcloud / nextcloud/notify_push
Add support for specifying base path
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
It would be great if while proxying, only routing by path would need to be applied.
Adding base path to notify_push would solve that.
Why? For example:
https://serverfault.com/a/336784
Example:
add env var or cmdline argument to specify base path:
PUSH_BASE_PATH=https://your_nextcloud_address/push
After that you'd only need to route https://your_nextcloud_address/push/* to notify server in reverse proxy.
Contributor guide
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 notify_push's configuration and startup entry points for existing environment variables or command-line arguments, then trace how proxied request paths are handled. Done means a configurable base path is accepted and requests under that path can be routed to the notify server as described, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100