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

Added a comment: Re: comment 1

Browse source
This commit is contained in:
https://christian.amsuess.com/chrysn 2020-09-17 20:42:12 +00:00 committed by admin
parent f2cdacdb68
commit b301a64aa2
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/httpalso_mode_expects_encryption/comment_2_5f31ee4052f7b0203aa287b5ec9abcab._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="https://christian.amsuess.com/chrysn"
nickname="chrysn"
avatar="http://christian.amsuess.com/avatar/c6c0d57d63ac88f3541522c4b21198c3c7169a665a2f2d733b4f78670322ffdc"
subject="Re: comment 1"
date="2020-09-17T20:42:10Z"
content="""
In my use case, I'd actually declare access the regular remotes with exporttree=true -- because the HTTP server serves only the checkout, and does not even give access to the .git repository. For this case, I don't see how declaring a regular git HTTP remote would help.
Apart from that, a declared httpalso remote on exporttree=no would also make the HTTP server available using enableremote. That is especially beneficial because git-annex on its own seems to be unable to derive the git-annex UUID for an HTTP git remote on a dumb server. (Serving only the files and running `git update-server-info`, I could do a `git fetch`, but an annex sync would always give \"Remote origin-via-http not usable by git-annex; setting annex-ignore\" until I set remote.origin-via-http.annex-uuid manually, and then fetching did work.)
"""]]