9 ms·
That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale. How does somepla
by mbreese 23d ago
That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale.
How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?
- crabmusket 23d agoThis recent post that made it to the front page talks a lot about approaches GitHub has taken over its history: https://cursor.com/blog/git-at-any-scale https://cursor.com/blog/git-at-any-scale
- mbreese 22d agoI ended up finding my own answer (after reading the above). https://nesbitt.io/2026/02/26/git-in-postgres.html https://nesbitt.io/2026/02/26/git-in-postgres.html Following another recent theme, the answer for Forgejo seems to be - just use Postgres.
- jeremyjh 22d agoThat approach was mentioned in the Cursor article. If a KV cache like Redis is too slow for that to work with large repositories, I don't see how Postgres could possibly work.