summaryrefslogtreecommitdiff
path: root/doc/devblog
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-06-05 16:39:10 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-06-05 16:39:10 -0400
commit751d27ea1012332b7ff25bca32ed5950135713d4 (patch)
tree5f3f329f690d8470ababaed6e8f05f43bced5fe4 /doc/devblog
parent8aead31319843e47296056c9d4172e70be107cfe (diff)
devbog
Diffstat (limited to 'doc/devblog')
-rw-r--r--doc/devblog/day_291__public_S3.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/devblog/day_291__public_S3.mdwn b/doc/devblog/day_291__public_S3.mdwn
new file mode 100644
index 000000000..7d00643a9
--- /dev/null
+++ b/doc/devblog/day_291__public_S3.mdwn
@@ -0,0 +1,16 @@
+Now git-annex can be used to set up a public S3 remote. If you've cloned a
+repository that knows about such a remote, you can use the S3 remote
+without needing any S3 credentials. Read-only of course.
+
+This tip shows how to do it: [[tips/public_Amazon_S3_remote]]
+
+That will work for at least AWS S3, and for the Internet Archive's S3.
+It may work for other S3 services, that can be configured to publish
+their files over unauthenticated http. There's a `publicurl` configuration
+setting to allow specifying the url when using a service that git-annex
+doesn't know the url for.
+
+Actually, there was a hack for the IA before, that added the public url to
+an item when it was uploaded to the IA. While that hack is now not
+necessary, I've left it in place for now, to avoid breaking anything that
+depended on it.