+To serve gitweb at the same url, use a ScriptAliasMatch to only
+those URLs that git http-backend can handle, and forward the
+rest to gitweb:
+
+
+
+ScriptAliasMatch \
+ \"(?x)^/git/(.*/(HEAD | \
+ info/refs | \
+ objects/(info/[^/]+ | \
+ [0-9a-f]{2}/[0-9a-f]{38} | \
+ pack/pack-[0-9a-f]{40}\.(pack|idx)) | \
+ git-(upload|receive)-pack))$\" \
+ /usr/libexec/git-core/git-http-backend/$1
+
+ScriptAlias /git/ /var/www/cgi-bin/gitweb.cgi/
+
+
+
+
+If you add the following AliasMatch between the two ScriptAlias directives, you can get Apache to serve the (...).git/config file to the http client, in this case git-annex.
+
++AliasMatch \"(?x)^/git/(.*/config)$\" /var/www/git/$1 ++ +This allows the annexes to use the autoenable=true to pin the centralisation afforded by the git only repository. Keep a \"source of truth\" so to speak (acknowledging that this is antithetical to what git-annex aims to do). + +As an aside, the tip to generate a uuid didn't seem to work for me. But I suspect I missed the point somewhat. + +Regardless, if you are able to alter the configuration of your \"centralised\" git repository, this might be of assistance. + +[id]: https://git-scm.com/docs/git-http-backend \"git-http-backend\" +"""]]