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

correct S3 environment variable names

Browse source
This commit is contained in:
Joey Hess 2012-05-29 15:01:36 -04:00
parent a8ab3c6123
commit f97009fffe
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/special_remotes/S3.mdwn
View file

@ -6,8 +6,8 @@ See [[tips/using_Amazon_S3]] and
## configuration ## configuration
The standard environment variables `ANNEX_S3_ACCESS_KEY_ID` and The standard environment variables `AWS_S3_ACCESS_KEY_ID` and
`ANNEX_S3_SECRET_ACCESS_KEY` are used to supply login credentials `AWS_S3_SECRET_ACCESS_KEY` are used to supply login credentials
for Amazon. When encryption is enabled, they are stored in encrypted form for Amazon. When encryption is enabled, they are stored in encrypted form
by `git annex initremote`, so you do not need to keep the environment by `git annex initremote`, so you do not need to keep the environment
variables set after the initial initalization of the remote. variables set after the initial initalization of the remote.

4
doc/tips/using_Amazon_S3.mdwn
View file

@ -4,8 +4,8 @@ Amazon S3, and use git-annex to transfer files into the cloud.
First, export your S3 credentials: First, export your S3 credentials:
# export ANNEX_S3_ACCESS_KEY_ID="08TJMT99S3511WOZEP91" # export AWS_S3_ACCESS_KEY_ID="08TJMT99S3511WOZEP91"
# export ANNEX_S3_SECRET_ACCESS_KEY="s3kr1t" # export AWS_S3_SECRET_ACCESS_KEY="s3kr1t"
Now, create a gpg key, if you don't already have one. This will be used Now, create a gpg key, if you don't already have one. This will be used
to encrypt everything stored in S3, for your privacy. Once you have to encrypt everything stored in S3, for your privacy. Once you have