nextcloud / nextcloud/recognize
Exclude models from updater backup
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Describe the feature you'd like to request
Updating my Nextcloud via webinterface is no longer possible, since the updater tries for ages to backup the models under apps/recognize/models (as well as /apps/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib tensorflow.so – three times thanks to not supporting symlinks).
Describe the solution you'd like
Download the models to data/ instead? That's ignored by the updater AFAIK.
Describe alternatives you've considered
Modifying/configuring the updater to exclude the path apps/recognize/models? Don't know if that's a supported feature.
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 tracing how the updater handles apps/recognize/models and how the app downloads or locates its models. Check the handling of apps/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib tensorflow.so as well. Done means model files are not included in the updater backup while recognition continues to work after an update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, tensorflow
- Domain
- backend, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100