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

update

Browse source
This commit is contained in:
Joey Hess 2024-06-12 15:21:23 -04:00
parent 46a1fcb3ea
commit 0ebb107974
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 13 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/design/passthrough_proxy.mdwn
View file

@ -166,6 +166,17 @@ If the user later does `git-annex copy --to proxy-bar`, it would avoid
another upload (and the user would learn at that point that it was in another upload (and the user would learn at that point that it was in
proxy-bar). This avoids needing to change the `storeKey` interface. proxy-bar). This avoids needing to change the `storeKey` interface.
Should a proxy always fanout? if `git-annex copy --to proxy` is what does
fanout, and `git-annex copy --to proxy-foo` doesn't, then the user has
content. But if the latter does fanout, that might be annoying to users who
want to use proxies, but want full control over what lands where, and don't
want to use preferred content to do it. So probably fanout should be
configurable. But it can't be configured client side, because the fanout
happens on the proxy. Seems like remote.name.annex-fanout could be set to
false to prevent fanout to a specific remote. (This is analagous to a
remote having `git-annex assistant` running on it, it might fan out uploads
to it to other repos, and only the owner of that repo can control it.)
A command like `git-annex push` would see all the instantiated remotes and A command like `git-annex push` would see all the instantiated remotes and
would pick ones to send content to. If the proxy does fanout, this would would pick ones to send content to. If the proxy does fanout, this would
lead to `git-annex push` doing extra work iterating over instantiated lead to `git-annex push` doing extra work iterating over instantiated

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

@ -44,10 +44,10 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
* Consider getting instantiated remotes into git remote list. * Consider getting instantiated remotes into git remote list.
See design. See design.
* Implement single upload with fanout to proxied remotes.
* Implement clusters. * Implement clusters.
* Implement single upload with fanout to proxied remotes.
* Support proxies-of-proxies better, eg foo-bar-baz. * Support proxies-of-proxies better, eg foo-bar-baz.
Currently, it does work, but have to run `git-annex updateproxy` Currently, it does work, but have to run `git-annex updateproxy`
on foo in order for it to notice the bar-baz proxied remote exists, on foo in order for it to notice the bar-baz proxied remote exists,