Post #1107143
2026-04-06 04:53 UTC
Okay, one issue I have with Forgejo right now is that somehow the cache TTL for commit metadata in the web interface is too short.
I have it at the current defaults, and it looks like Forgejo refetches the commit metadata every hour or so :/
Any idea if there's a background job I can trigger to automagically keep the cache "warm"?
Replies (1)
-
@felsqualle@manitu.social 2026-04-06 05:52
And another thing: every time I clone a fairly large repository, the initial step takes quite long, almost like compression going on on the remote each and every time. Couldn’t replicate this with GitHub, so not really sure where to look into.