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
35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
Made a release today. Releasing has sure gotten easier with all the
|
|
autobuilds to use!
|
|
|
|
I am now using git-annex to share files with my mom. Here's how the webapp
|
|
looks for our family's repository. Soon several of us will be using this
|
|
repository.
|
|
|
|
[[!img assistant/example.png]]
|
|
|
|
We're using XMPP and rsync.net, so pretty standard setup much like
|
|
shown in my last screencast.
|
|
|
|
Real-world deployments help find bugs, and I found a few:
|
|
|
|
* If you're running the webapp in `w3m` on a remote computer to set it up,
|
|
some forms are lacking submit buttons. This must be a issue with
|
|
Bootstrap, or HTML5, I guess. I switched to `lynx` and it offers a
|
|
way to submit forms that lack an explicit button.
|
|
|
|
* Progress bars for downloads from encrypted rsync repos don't update
|
|
during the actual download, but only when gpg is decrypting the
|
|
downloaded file.
|
|
|
|
* XMPP pushes sometimes fail still. Especially when your mom's computer
|
|
is saturating its limited outgoing network connection uploading hundreds of
|
|
photos. I have not yet determined if this is a packet loss/corruption issue,
|
|
or if the XMPP messages are getting out of order. My gut feeling is it's
|
|
the latter, in which can I can fix this pretty easily by adding sequence
|
|
numbers and some buffering for out of order packets. Or perhaps just
|
|
make it retry failed pushes when this happens.
|
|
|
|
Anyway, I found it was useful to set up a regular git repository on a
|
|
server to suppliment the git pushes over XMPP. It's helpful to have
|
|
such a git repository anyway, so that clients can push to there when the
|
|
other client(s) are not online to be pushed to directly over XMPP.
|