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
43 lines
1.5 KiB
Markdown
43 lines
1.5 KiB
Markdown
Currently, git-annex takes a very lazy approch to displaying
|
|
progress into. It just lets rsync or whatever display the progress
|
|
for it, in the terminal.
|
|
|
|
Something better is needed for the [[webapp]]. There needs to be a
|
|
way for the web app to know what the current progress is of all transfers.
|
|
|
|
This is one of those potentially hidden but time consuming problems.
|
|
|
|
## downloads
|
|
|
|
* Watch temp file as it's coming in and use its size.
|
|
Can either poll every .5 seconds or so to check file size, or
|
|
could use inotify. **done**
|
|
* When easily available, remotes call the MeterUpdate callback as downloads
|
|
progress. **done**
|
|
* S3 TODO
|
|
While it has a download progress bar, `getObject` probably buffers the whole
|
|
download in memory before returning. Leaving the progress bar to only
|
|
display progress for writing the file out of memory. Fixing this would
|
|
involve making hS3 stream better (also avoids it wasting memory).
|
|
|
|
## uploads
|
|
|
|
Each individual remote type needs to implement its own support for calling
|
|
the MeterUpdate callback as the upload progresses.
|
|
|
|
* git: **done**
|
|
* rsync: **done**
|
|
* directory: **done**
|
|
* web: Not applicable; does not upload
|
|
* webdav: **done**
|
|
* S3: **done**
|
|
* glacier: **done**
|
|
* bup: TODO
|
|
* hook: Would require the hook interface to somehow do this, which seems
|
|
too complicated. So skipping.
|
|
|
|
## communication
|
|
|
|
It may be worth using a better communication channel than files on disk for
|
|
the transfer progress. Shared memory could be used, or http posts to the
|
|
webapp.
|