Recent searches
Search options
So who wants to help the @Codeberg folks implement code search?
Codeberg.orgCode Search: Looking for maintainersAn existing issue (#379) tracks the feature to enable code search on Codeberg.
To move this forward, I'd appreciate to create a team of people available to experiment with it and maintain the setup in the future.
The plan could look as follows:
- discuss the resource allocations regarding memory, CPU and disk storage with the Codebeg infrastructure team
- an LXC container is created matching the above results on our infrastructure
- investigate the use of [ZincSearch](https://github.com/zinclabs/zinc) vs OpenSearch
- configurate Forgejo / Gitea to connect to the setup using a test instance
- adapt and finish [this pull request](https://codeberg.org/Codeberg/forgejo/pulls/47) to enable code search per repository (opt-in)
- enable code search on the production instance and continue the maintenance of the setups inside the LXC container
If this sounds interesting to you, please reach out here. We're available to collaborate closely with you, however it would be great if a dedicated team could push the effort and iterate independently.
Thank you a lot!
Useful links:
- Forgejo config: https://docs.gitea.io/en-us/config-cheat-sheet/#indexer-indexer
- #379 with experiences
- connect Forgejo to ZincSearch: https://github.com/zinclabs/zinc/issues/538#issuecomment-1251748395
- consider Sourcegraph as an alternative to Forgejo-built-in search: https://about.sourcegraph.com/
@aral@mastodon.ar.al @Codeberg@social.anoxinon.de On what day would you like us to talk about this?