mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

proxy updates location tracking information

Browse source 
This does mean a redundant write to the git-annex branch. But,
it means that two clients can be using the same proxy, and after
one sends a file to a proxied remote, the other only has to pull from
the proxy to learn about that. It does not need to pull from every
remote behind the proxy (which it couldn't do anyway as git repo
access is not currently proxied).

Anyway, the overhead of this in git-annex branch writes is no worse
than eg, sending a file to a repository where git-annex assistant
is running, which then sends the file on to a remote, and updates
the git-annex branch then. Indeed, when the assistant also drops
the local copy, that results in more writes to the git-annex branch.
This commit is contained in:
Joey Hess 2024-06-12 11:37:14 -04:00
parent 96853cd833
commit dfdda95053
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 66 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/todo/git-annex_proxies.mdwn
View file

@ -39,10 +39,7 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
3. Implement git-annex-shell proxying to git remotes. (done)
3. Proxy should update location tracking information for proxied remotes,
so it is available to other users who sync with it.
4. Either implement proxying for tor-annex remotes, or prevent
listProxied from operating on them.
so it is available to other users who sync with it. (done)
4. Let `storeKey` return a list of UUIDs where content was stored,
and make proxies accept uploads directed at them, rather than a specific
@ -71,3 +68,4 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
11. indirect uploads (to be considered). See design.
12. Support using a proxy when its url is a P2P address.
(Eg tor-annex remotes.)