this is not all run as root

This commit is contained in:
Joey Hess 2019-03-27 11:15:03 -04:00
parent 77a1e33093
commit f4c49b8f81
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
22 changed files with 89 additions and 89 deletions

View file

@ -19,14 +19,14 @@ environment variables. Don't worry -- it will prompt if you leave anything off.
So feel free to make any kind of special remote instead of the S3 remote
used in this example.
# export AWS_ACCESS_KEY_ID="somethingotherthanthis"
# export AWS_SECRET_ACCESS_KEY="s3kr1t"
# git annex initremote mys3 type=S3 chunk=1MiB encryption=shared
$ export AWS_ACCESS_KEY_ID="somethingotherthanthis"
$ export AWS_SECRET_ACCESS_KEY="s3kr1t"
$ git annex initremote mys3 type=S3 chunk=1MiB encryption=shared
initremote mys3 (shared encryption) (checking bucket) (creating bucket in US) ok
Now you can store files on the newly initialized special remote.
# git annex copy my_cool_big_file --to mys3
$ git annex copy my_cool_big_file --to mys3
copy my_cool_big_file (to mys3...) ok
Once you've initialized a special remote in one repository, you can enable
@ -38,15 +38,15 @@ To do so, first get git-annex in sync (so it knows about
the special remote that was added in the other repository), and then
use `git annex enableremote`.
desktop# git annex sync
desktop# export AWS_ACCESS_KEY_ID="somethingotherthanthis"
desktop# export AWS_SECRET_ACCESS_KEY="s3kr1t"
desktop# git annex enableremote mys3
desktop$ git annex sync
desktop$ export AWS_ACCESS_KEY_ID="somethingotherthanthis"
desktop$ export AWS_SECRET_ACCESS_KEY="s3kr1t"
desktop$ git annex enableremote mys3
enableremote mys3 (checking bucket) ok
And now you can download files from the special remote:
desktop# git annex get my_cool_big_file --from mys3
desktop$ git annex get my_cool_big_file --from mys3
get my_cool_big_file (from mys3...) ok
This has only scratched the surface of what can be done with