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

git-remote-annex enableremote to support readonly webdav

Browse source 
* Allow enableremote of an existing webdav special remote that has
  read-only access.
* git-remote-annex: Use enableremote rather than initremote.
This commit is contained in:
Joey Hess 2025-01-07 15:57:20 -04:00
parent e7e479c1f0
commit 5d2aaafa6c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 39 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

25
doc/todo/Read-only_support_for_webdav/comment_1_1fd87a5ab19a81a1b094efea7e70e581._comment Normal file
View file

@ -0,0 +1,25 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2025-01-07T18:51:26Z"
content="""
I'm not sure I'd trust an old comment of mine to reflect whether httpalso
supports http authentication. From what I can see, without trying it, it
will use git-credential to prompt for password when receiving a 401
response, the same as all other parts of git-annex that download urls
do nowadays.
Re git-remote-annex, I see your point though. Since it does set up the
remote when cloning, and webdav remote setup calls involves creating and
deleting a test file, the user needs write access currently. (Whether that
test file is worth it doing at all, I'm on the fence about. It seemed like
a good idea way back when.)
I think that, rather than needing readonly=true, enableremote of a webdav
special remote should just assume it exists and not test write access to
it. Then it will work with readonly access. I've implemented that.
And I've made git-remote-annex on git clone do an enableremote, rather than
an initremote. That should make it work with a readonly webdav special
remote.
"""]]