Make the S3 caching available for "slower" mapped non-S3 datafolders
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
I have mapped a (slower) network NAS drive mapped to the data folder of Nextcloud via fstab (linux).
But wouldn't it improve performance if that folder was cached.. Nextcloud has cashing built in when data is stored via S3. Could that caching technique also be activated via a config setting? I think that wouldn't be that much work (for a person knowing where to look ;) and it would be a nice option to speed things up :)
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 tracing Nextcloud’s existing S3 caching path and the configuration entry points for data folders; the issue names no files or tests. Determine whether the same caching can safely apply to an fstab-mounted NAS data folder, then define the configuration behavior and validation needed for the feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, php
- Domain
- backend, cloud, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100