b6d46c212e
* 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
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
Amazon S3 was the second most popular choice in the
|
|
[[polls/prioritizing_special_remotes]] poll, and since I'm not sure how
|
|
I want to support phone/mp3 players, I did it first.
|
|
|
|
So I added a configurator today to easily set up an Amazon S3 repository.
|
|
That was straightforward and didn't take long since git-annex already
|
|
supported S3.
|
|
|
|
The hard part, of course, is key distribution. Since the webapp so far
|
|
can only configure the shared encryption method, and not fullblown gpg keys,
|
|
I didn't feel it would be secure to store the S3 keys in the git repository.
|
|
Anyone with access to that git repo would have full access to S3 ... just not
|
|
acceptable. Instead, the webapp stores the keys in a 600 mode file locally,
|
|
and they're not distributed at all.
|
|
|
|
When the same S3 repository is enabled on another computer, it prompts for
|
|
keys then too. I did add a hint about using the IAM Management Console in
|
|
this case -- it should be possible to set up users in IAM who can only
|
|
access a single bucket, although I have not tried to set that up.
|
|
|
|
---
|
|
|
|
Also, more work on the standalone OSX app.
|