Deployment: Permit CodeSearch for blender/ repos #31

Open
opened 2023-02-14 11:32:15 +01:00 by Arnd Marijnissen · 1 comment

Currently we have no way of supporting code-search without risking running out of disk really quickly.
The documentation lists that code-search requires about 6 times the disk-space of the repo involved.

Code-search has a few controls we can use to govern its functioning; however, not enough to quite do what we'd like it to do (by default).

  • It permits 'bleve' (local) indexing or using ElasticSearch
  • It does not have controls in Gitea (yet) that'd permit restricting it to 'interesting'/'relevant' repositories.

In the interest of scalability, it'd seem logical to consider ElasticSearch backend as being the most useful. It might be possible to filter out the data we want indexed on the side of ElasticSearch. This'd permit us to enable 'REPO_INDEXER' on the short term, at the expense of it indexing things that we dont store the data for. Ultimately, a control in Gitea/repos to disable indexing would be the best solution.

Currently we have no way of supporting code-search without risking running out of disk really quickly. The documentation lists that code-search requires about 6 times the disk-space of the repo involved. Code-search has a few controls we can use to govern its functioning; however, not enough to quite do what we'd like it to do (by default). * It permits 'bleve' (local) indexing or using ElasticSearch * It does not have controls in Gitea (yet) that'd permit restricting it to 'interesting'/'relevant' repositories. In the interest of scalability, it'd seem logical to consider ElasticSearch backend as being the most useful. It might be possible to filter out the data we want indexed on the side of ElasticSearch. This'd permit us to enable 'REPO_INDEXER' on the short term, at the expense of it indexing things that we dont *store* the data for. Ultimately, a control in Gitea/repos to disable indexing would be the best solution.
Arnd Marijnissen added the
gitea feature request
deployment
labels 2023-02-14 11:32:15 +01:00

Tracked in the following upstream issue: https://github.com/go-gitea/gitea/issues/22842

Tracked in the following upstream issue: https://github.com/go-gitea/gitea/issues/22842
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#31
No description provided.