Fixes to the S3 walk-through

[adswa]

This incorporates the corrected commands and information from #1224.
Fixes #1224.

[adswa]

hey @all-contributors please add @NickleDave for bug, content

[allcontributors]

@adswa

I've put up a pull request to add @NickleDave! 🎉

[mslw]

I believe we should also mention the publicurl git-annex parameter. Otherwise, I think git-annex would use s3 protocol, and I am not sure if it does it anonymously. See its description in git-annex S3 manpage.

There is, however, a caveat that the git-annex available currently in debian-stable does not recognize the publicurl parameter, and blindly follows public 🙈 I think this is worth another find-out-more. See also this comment.

[adswa]

There is, however, a caveat that the git-annex available currently in debian-stable does not recognize the publicurl parameter, and blindly follows public 🙈 I think this is worth another find-out-more. See also #1224 (comment).

I have added a version note to the top of the page, and I also linked the discussion in it.

I believe we should also mention the publicurl git-annex parameter. Otherwise, I think git-annex would use s3 protocol, and I am not sure if it does it anonymously. See its description in git-annex S3 manpage.

Do you mean beyond the description prior to enableremote?

I realize I haven't mentioned the bucket policies - I will read up on what they are and add a findoutmore on them.

[mslw]

Ah, sorry, publicurl has already been there, I focused on the diff, and the part which removed public -- but at that stage in the chapter we are assuming that everything is private.

So it isn't exactly as bad as what I said (that older annex does not recognize publicurl at all -- it does not recognize it when public=no). You can check again whether the important note at the top is not too strict (because of me), but otherwise I retract my request for changes :-)