diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-06-05 16:43:03 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-06-05 16:43:03 -0400 |
commit | 4370bf61b8314918fb503bab66556b7b4c79b54d (patch) | |
tree | bca48b65aee7e039c6e3092050321d5f85357891 | |
parent | acdef5be17d1695dac258f795b8a89930a5ad412 (diff) |
improve
-rw-r--r-- | doc/tips/public_Amazon_S3_remote.mdwn | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/tips/public_Amazon_S3_remote.mdwn b/doc/tips/public_Amazon_S3_remote.mdwn index 0140445c4..a1fb7f6f2 100644 --- a/doc/tips/public_Amazon_S3_remote.mdwn +++ b/doc/tips/public_Amazon_S3_remote.mdwn @@ -17,12 +17,16 @@ Now, create the remote: # git annex initremote pubs3 type=S3 encryption=none public=yes initremote pubs3 (checking bucket) (creating bucket in US) ok -In the above example, no encryption was used, but it will also work -if you enable eg, encryption=shared. It's also ok to enable chunking. - The public=yes is the crtical part; this lets the public read the contents of the bucket. +In the above example, no encryption was used, but it will also work +if you enable encryption=shared. Then files will be encrypted on S3, and +anyone with a clone of the git repository will be able to download and +decrypt them. + +It's also ok to enable chunking when setting up the remote. + Now, copy some files to the remote, in the usual way, and push your git repository to someplace where someone else can access it. |