[Feature] High Performance File Backend
Open
Nobody has claimed this yet.
enhancement
Persistence
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Are you planning to include the High Performance File Backend aka Client Push in the Helm chart or would you accept a pull request that adds this? This might be related to #106 as Nextcloud 21 is a base requirement for that.
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 reading the Helm chart's templates and values, then compare the requested High Performance File Backend (Client Push) with issue #106 and its Nextcloud 21 requirement. Confirm the chart's expected configuration and deployment behavior before making changes. Done means the backend can be enabled through the chart without breaking existing deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100