Deployment: Permit CodeSearch for blender/ repos #31
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#31
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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).
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.
Tracked in the following upstream issue: https://github.com/go-gitea/gitea/issues/22842