change copySizeLimit to a value larger than the default `5242880000` not working
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Describe your Issue
It's a common case that user could upload files that larger than 5GB, and when using s3 backend, it's limited by copySizeLimit parameter.
Logs and Errors
when uploading a file with 10GB, it finished uploading and report an unknown error.
Describe your Environment
-
Helm Chart Version: 6.6.4
-
values.yaml:
there is no option that could be configured in chart values.
instead, I modify the chart template directly and check the copySizeLimit to be taken into effect withocc config:list systemcommand.
Additional context, if any
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
Review the Helm chart template that sets Nextcloud's copySizeLimit and the chart's values/configuration path; confirm how the S3 backend receives this setting. Reproduce with a file larger than 5 GB and check occ config:list system plus upload behavior; done means values can configure a limit above 5242880000 without an unknown error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100