'database is locked' error under concurrent writes: gc default considerations for low-traffic Forgejo
This question addresses the optimal default setting for automatic repository garbage collection in Forgejo deployments designed for low-traffic workloads. The goal is to determine whether enabling automatic garbage collection by default yields net storage benefits without introducing unacceptable I/O latency during occasional push or pull‑request activity. K