
* unannex, uninit: Avoid committing after every file is unannexed, for massive speedup. * --notify-finish switch will cause desktop notifications after each file upload/download/drop completes (using the dbus Desktop Notifications Specification) * --notify-start switch will show desktop notifications when each file upload/download starts. * webapp: Automatically install Nautilus integration scripts to get and drop files. * tahoe: Pass -d parameter before subcommand; putting it after the subcommand no longer works with tahoe-lafs version 1.10. (Thanks, Alberto Berti) * forget --drop-dead: Avoid removing the dead remote from the trust.log, so that if git remotes for it still exist anywhere, git annex info will still know it's dead and not show it. * git-annex-shell: Make configlist automatically initialize a remote git repository, as long as a git-annex branch has been pushed to it, to simplify setup of remote git repositories, including via gitolite. * add --include-dotfiles: New option, perhaps useful for backups. * Version 5.20140227 broke creation of glacier repositories, not including the datacenter and vault in their configuration. This bug is fixed, but glacier repositories set up with the broken version of git-annex need to have the datacenter and vault set in order to be usable. This can be done using git annex enableremote to add the missing settings. For details, see http://git-annex.branchable.com/bugs/problems_with_glacier/ * Added required content configuration. * assistant: Improve ssh authorized keys line generated in local pairing or for a remote ssh server to set environment variables in an alternative way that works with the non-POSIX fish shell, as well as POSIX shells. # imported from the archive
37 lines
1.4 KiB
Markdown
37 lines
1.4 KiB
Markdown
git-annex extends git's usual remotes with some [[special_remotes]], that
|
|
are not git repositories. This way you can set up a remote using say,
|
|
Amazon S3, and use git-annex to transfer files into the cloud.
|
|
|
|
First, export your Amazon AWS credentials:
|
|
|
|
# export AWS_ACCESS_KEY_ID="08TJMT99S3511WOZEP91"
|
|
# export AWS_SECRET_ACCESS_KEY="s3kr1t"
|
|
|
|
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
|
|
a gpg key, run `gpg --list-secret-keys` to look up its key id, something
|
|
like "2512E3C7"
|
|
|
|
Next, create the S3 remote, and describe it.
|
|
|
|
# git annex initremote cloud type=S3 keyid=2512E3C7
|
|
initremote cloud (encryption setup with gpg key C910D9222512E3C7) (checking bucket) (creating bucket in US) (gpg) ok
|
|
# git annex describe cloud "at Amazon's US datacenter"
|
|
describe cloud ok
|
|
|
|
The configuration for the S3 remote is stored in git. So to make another
|
|
repository use the same S3 remote is easy:
|
|
|
|
# cd /media/usb/annex
|
|
# git pull laptop
|
|
# git annex initremote cloud
|
|
initremote cloud (gpg) (checking bucket) ok
|
|
|
|
Now the remote can be used like any other remote.
|
|
|
|
# git annex copy my_cool_big_file --to cloud
|
|
copy my_cool_big_file (gpg) (checking cloud...) (to cloud...) ok
|
|
# git annex move video/hackity_hack_and_kaxxt.mov --to cloud
|
|
move video/hackity_hack_and_kaxxt.mov (checking cloud...) (to cloud...) ok
|
|
|
|
See [[special_remotes/S3]] for details.
|