nextcloud / nextcloud/richdocuments
Setup warnings for common issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
We should register setup checks for what we already check with #3315
Ref https://github.com/nextcloud/server/pull/32550
In addition the following could be useful:
-
Background job status of fetching capabilties/discovery
-
Issues with larger file saving (wopi POST)
- max_execution_time
- post_max_size
- upload_max_size
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 reviewing issue #3315 and the referenced Nextcloud pull request to identify the existing checks that should receive setup warnings. Then inspect how richdocuments registers setup checks and cover the listed background-job and WOPI saving conditions, including the named PHP limits; done means each requested condition produces an appropriate warning.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100