thejosh
Joined 14 years ago
Joined 14 years ago
I can't believe how many critical bugs fall through.
My favourite one is the bug where Plan mode can execute destructive commands inadvertently.
Then all these get closed with `Closing for now — inactive for too long. Please open a new issue if this is still relevant.`. Awesome.
For context, forgejo does have [code search](https://forgejo.org/docs/latest/user/search/code-search/), which is simple to enough.
I like forgejo/gitea - a single app.ini, postgres for the database. Done through a docker compose.
Last time I ran gitlab, it required oodles of memory - it's just me!
> You can just self-host GitLab CE and use self-hosted ElasticSearch integration to set up code search. I really don't understand the point of Forgejo, sounds like making your life harder
Sounds like more steps/maintenance/hassle and a more complicated than just using forgejo for my own personal projects, forgejo uses <120MB of memory for me, has runners, etc.
Codeberg sounds great, but from using it day-to-day, it's really slow sometimes, and frequently times out (from Perth, AU, if it matters). This is not just the SSH protocol for git pushes, but also for browsing.
(I do have a self-hosted forgejo (came from gitea), it's great, Postgres database backs up, files are easy to backup, it's also git so I can just mirror it elsewhere as well.). I love their self-hosted runners is super simple to host.
Bit random, but for code search, does anyone have any recommendations?
My current process is to just `git clone <REPO>` onto my server, then use ripgrep (Can't beat good ol' plain text search).
The result is that this is hundreds of GB -- I like to clone everything I use, dependencies etc, to then be able to look at source code. (I use quite a few languages/ecosystems, and sometimes reading the source code is the best way to figure something out).
I've tried Sourcebot (just for the code search, I don't care about "MCP"/"AI") etc, but was wondering if anyone has recommendations.
GitHubs code search is great, but it doesn't find everything, and it is also incredibly rate limited (annoying when trying to narrow something down, and you then get rate limited). I use this when trying to figure out random Apple issues - someone somewhere has figured it out usually.