Support additional Nextcloud-occ's housekeeping functions
Open
Nobody has claimed this yet.
daemon
daemon-api
enhancement
nextcloud
- Dominant language
- Python
- Stars
- 38
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
-
occ upgrade(as job: yes. to api: no) can be run from within a (recurring) job to avoid the upgrade view for the user -
occ trash(as job: yes, to api: no) might be useful before backups? -
occ maintenance:repair(as job: ?, to api: yes) does a good fixing various issues automagically -
occ db:add-missing-indices(as job: ?, to api: yes) Nextcloud recommends this (to improve performance) insettings -> overview -> Security & setup warnings
Contributor guide
No contributing guide indexed for this repository
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 locating the existing support for occ upgrade and its job or API entry points. Compare how occ trash, occ maintenance:repair, and occ db:add-missing-indices should be exposed, then verify which job and API paths are appropriate for each command. Done means the selected housekeeping functions are supported with their intended interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100