On Fri, Jan 17, 2014 at 02:29:19PM -0500, Konstantin Ryabitsev wrote: > On 17/01/14 01:22 PM, Jason A. Donenfeld wrote: > >> But scan for repos is caught by the cache most of the time, and > >> > presumably even if we run persistently we still need to do that > >> > periodically (or use inotify); or do we just rely on the process being > >> > replaced when the set of repositories changes? > > Generally the idea is you restart the fcgi process when things change, > > or at least send it a SIGUSR1. But we could be fancy and support > > inotify/kqueue... > > The process that updates the repositories may not have permissions to > send SIGUSR1 to the fcgid process -- either because they are running as > different users or because there are SELinux policies preventing it. > > It's really best if cgit recognizes when things like projects.list have > changed.
Presumably you are OK with this having the same latency as the existing cache mechanism. The simplest implementation will probably be to keep the existing "cache valid?" check and re-scan repositories as we currently do. _______________________________________________ CGit mailing list CGit@lists.zx2c4.com http://lists.zx2c4.com/mailman/listinfo/cgit