Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support additional Nextcloud-occ's housekeeping functions #55

Open
1 of 4 tasks
daringer opened this issue Apr 11, 2021 · 0 comments
Open
1 of 4 tasks

Support additional Nextcloud-occ's housekeeping functions #55

daringer opened this issue Apr 11, 2021 · 0 comments
Labels
daemon daemon backend functionalites daemon-api anything exposed through the daemon rest-api enhancement New feature or request nextcloud nextcloud and related

Comments

@daringer
Copy link
Collaborator

daringer commented Apr 11, 2021

  • 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) in settings -> overview -> Security & setup warnings
@daringer daringer changed the title Support additional Nextcloud occ housekeeping functions Support additional Nextcloud-occ's housekeeping functions Apr 11, 2021
@daringer daringer transferred this issue from Nitrokey/nextbox-daemon Jan 14, 2022
@daringer daringer added daemon daemon backend functionalites daemon-api anything exposed through the daemon rest-api enhancement New feature or request nextcloud nextcloud and related labels Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
daemon daemon backend functionalites daemon-api anything exposed through the daemon rest-api enhancement New feature or request nextcloud nextcloud and related
Projects
None yet
Development

No branches or pull requests

1 participant