update
This commit is contained in:
parent
d8fb366cf7
commit
1dd4b17bdf
1 changed files with 8 additions and 8 deletions
|
@ -10,12 +10,12 @@ own key names (although typically done before data is stored in it),
|
||||||
but a tahoe-lafs special remote would be more flexible.
|
but a tahoe-lafs special remote would be more flexible.
|
||||||
|
|
||||||
To support a special remote, a mapping is needed from git-annex keys to
|
To support a special remote, a mapping is needed from git-annex keys to
|
||||||
Tahoe keys.
|
Tahoe keys, stored in the git-annex branch.
|
||||||
|
|
||||||
The best place to store this mapping is perhaps as a new field in the
|
> This is now done, however, there are 2 known
|
||||||
location log:
|
> problems:
|
||||||
|
>
|
||||||
date present repo-uuid newfields
|
> * 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>
|
||||||
This way, each remote can store its own key-specfic data in the same place
|
>
|
||||||
as other key-specific data, with minimal overhead.
|
> --[[Joey]]
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue