nextcloud / nextcloud/notify_push
Custom prefix for Redis keys and channels
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
I want to use Redis ACL to improve the security of my installation, so I need to assign a namespace to Nextcloud. Currently, notify_push uses hardcoded key and channel names (it seems they all start with notify_ but I'm not sure if I can rely on thattest-token has no prefix), and I would like to set a custom prefix for them.
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
No file or test is named in the issue. Start by tracing where notify_push constructs Redis keys and channels and where its configuration is parsed; compare the behavior with the Redis ACL namespace requirement and the related Nextcloud server issue. Done means a configurable prefix applies consistently to the relevant keys and channels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100