Allow for (optional) Redis Key Prefix
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Support Namespacing in Redis
I've been looking into data separation in Redis. Nextcloud supports Redis ACL by allowing a username and password to be set. However, the way Nextcloud uses Redis makes it difficult to implement namespacing in Redis, i.e. to specify in the Redis access control list which user is allowed to access which keys. The Nextcloud keys apparently have the format <user-uuid>/locked/<file-uuid>.
Is your feature request related to a problem? Please describe.
Not that I see.
Describe the solution you'd like
The solution would be for Nextcloud to use (optionally definable) prefixes for its Redis keys, e.g. nextcloud:<uuid>/locked/<uuid>.
Describe alternatives you've considered
Do not support multi-client capability in Redis (which corresponds to the setup in most cases).
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
The issue names no files or tests. Start by locating how Nextcloud constructs and configures Redis keys, then determine where an optional prefix belongs and verify that the prefix is applied consistently without breaking existing deployments or ACL-based separation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100