nextcloud / nextcloud/previewgenerator
Add a limit to amount of previews that can be generated by a single call to pre-generate
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 520
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
Feature request
Which Nextcloud Version are you currently using: - 29.0.6
Sometimes user can add a folder to list of synchronizations in his NextCloud app, and this folder would have thousands of photos. This will lead to a situation when previews for all new photos will be generated during next call to pre-generate, making system very slow to respond to other requests, and maybe will even interrupt folder synchronization itself. Please add a limit to amount of previews that can be generated by a single call to pre-generate. Maybe even two limits: one total amount of previews and another per-user amount. Another idea is to have a limit on total size of files that can be processed during single call of pre-generate.
With this feature implemented, it should be possible to use nextcloud background jobs instead of manual shell commands.
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 the pre-generate call but no files, tests, or entry points. Start by locating that entry point and its related configuration or background-job documentation, then clarify whether limits are global, per-user, or size-based. Done requires an agreed limit behavior and tests covering the selected scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100