From dce9812e5f4b5b2bb520ffc93b9847cb6fcb2075 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 31 Oct 2026 17:48:01 -1000 Subject: Key the cached scan on every setting it uses Two cgitrc files sharing a cache-root read one list, so strict-export and trust-scan-config set in one applied to the other, and a changed setting stayed stale until the list expired. The first request after an upgrade scans again, and the files under the old names are never read. --- MANUAL.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'MANUAL.txt') diff --git a/MANUAL.txt b/MANUAL.txt index 76c4a15..1fd3fcf 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -466,9 +466,11 @@ scan-hidden-path:: scan-path:: A path which is scanned for repositories. If caching is enabled, the - result is cached as a cgitrc include-file in the cache directory. If - project-list has been defined prior to scan-path, scan-path loads only - the directories listed in the file pointed to by project-list. A + result is cached as a cgitrc include-file in the cache directory, under + a name drawn from the path and every setting the scan depends on, so + configs that would scan differently never share one. If project-list + has been defined prior to scan-path, scan-path loads only the + directories listed in the file pointed to by project-list. A repository containing a file named "noweb" is skipped, the reverse of what "strict-export" checks. Only the global settings taken before the scan-path directive apply to each repository. That holds for every -- cgit 2.12.1