nextcloud / nextcloud/cookbook
Migrate recipe update process to nextcloud structures
Open
Nobody has claimed this yet.
Backend
enhancement
maintenance
php
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
We are using a custom code to enforce periodic sync of the recipe database. We should consider using dedicated structures for that by nextcloud like repair steps and Cron jobs.
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 locating the custom process that periodically synchronizes the recipe database, then inspect the Nextcloud repair-step and Cron-job structures mentioned in the issue. Done means the existing sync process has been migrated to those dedicated structures, with the periodic update behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100