Normally a git repository is not treated as a special remote, but as a git remote of the normal kind. Two exceptions to that are git-lfs and gcrypt special remotes.
But it is possible to register a git repository as a special remote. git-annex and git will use the remote the same as any normal git remote, but its url will be recorded in the repository. One benefit of doing this is it allows git-annex init to autoenable the remote.
To set up such a special remote:
git annex initremote myremote type=git location=ssh://... autoenable=true
Now git annex init
in each clone of the repository will autoenable myremote.
This only works for git repositories that have a git-annex uuid set, because special remotes have to have a uuid. So it cannot be used with git repositories that are not git-annex repositories.
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.
If you follow the git-http-backend documentation for serving repositories via Apache, you'll read this section:
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: