nextcloud / nextcloud/fulltextsearch
'occ fulltextsearch:index' integration into the app configuration.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Would it be possible in one of the next versions to build the first index without an occ command? For example, it is not possible to execute 'occ fulltextsearch:index' at Hetzner in the storage share. In case of a new installation the creation of the index should not take much time.
Or is it not possible because the web user has no rights for it?
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
Review the existing occ fulltextsearch:index entry point and how the app configuration handles new installations. Determine whether indexing can be triggered without the command in the Hetzner storage-share environment and how web-user permissions affect it; done means a documented, workable first-index path for new installations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100