From my experimentation it seems to be that git-annex does not discover the annex.url config after the initial clone of a repository. There are at least two situations in which this would be useful though:
- If the server-side supports p2phttp, but the repository is cloned with an older version of git-annex that doesn't, the annexurl won't be picked up even if the client-side git-annex is later updated to a version that does support p2phttp.
- Likewise, if the server-side initially didn't support p2phttp and didn't set
annex.urlwhen the repository was cloned, but is later updated to support it, git-annex doesn't automatically pick up this change.
This automatic discovery would be nice for p2phttp support in forgejo-aneksajo, as existing clones could automatically start making use of it as soon as the instance is updated to support it on the server-side and the git-annex version is updated to be recent enough on the client-side.
annex.urlsetting by unsettingremote.<name>.annex-uuidand then doinggit annex initagain or trying to copy something to the remote.<owner>/<repo>routing namespace. Having git-annex retrieve updated config data from remotes would make this change propagate to clones automatically, which would be nice I think.Even if it only re-checks when git-annex is going to use the remote (and not on every run of git-annex) that seems perhaps too often to check.
But if it checks less often than that, once per day or whatever, there will of course be a window where it has not yet noticed the change and uses the cached remote.name.annexUrl and potentially fails.
A balance might be that if it fails to connect to the remote.name.annexUrl, it could re-check it then.