e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
[[forum/tips:_special__95__remotes__47__hook_with_tahoe-lafs]] is a good
|
|
start, but Zooko points out that using Tahoe's directory translation layer
|
|
incurs O(N^2) overhead as the number of objects grows. Also, making
|
|
hash subdirectories in Tahoe is expensive. Instead it would be good to use
|
|
it as a key/value store directly. The catch is that doing so involves
|
|
sending the content to Tahoe, and getting back a key identifier.
|
|
|
|
This would be fairly easy to do as a [[backend|backends]], which can assign its
|
|
own key names (although typically done before data is stored in it),
|
|
but a tahoe-lafs special remote would be more flexible.
|
|
|
|
To support a special remote, a mapping is needed from git-annex keys to
|
|
Tahoe keys, stored in the git-annex branch.
|
|
|
|
> This is now done, however, there are 3 known
|
|
> problems:
|
|
>
|
|
> * tahoe start run unncessarily <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2149>
|
|
> * web.port can conflict <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2147>
|
|
> * Nothing renews leases, which is a problem on grids that expire.
|
|
> <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2212>
|
|
|
|
> --[[Joey]]
|