oops, didn't mean to commit these changes yet
This commit is contained in:
parent
290ff35b53
commit
a4fe6e037b
2 changed files with 0 additions and 23 deletions
3
debian/changelog
vendored
3
debian/changelog
vendored
|
@ -8,9 +8,6 @@ git-annex (5.20150813) UNRELEASED; urgency=medium
|
|||
* sync: Support --jobs
|
||||
* sync --content: Avoid unnecessary second pull from remotes when
|
||||
no file transfers are made.
|
||||
* External special remotes can now be built that can be used in readonly
|
||||
mode, where git-annex downloads content from the remote using regular
|
||||
http.
|
||||
|
||||
-- Joey Hess <id@joeyh.name> Wed, 12 Aug 2015 14:31:01 -0400
|
||||
|
||||
|
|
|
@ -343,26 +343,6 @@ quite a long time, especially when the git-annex assistant is using it.
|
|||
The assistant will detect when the system connects to a network, and will
|
||||
start a new process the next time it needs to use a remote.
|
||||
|
||||
## readonly mode
|
||||
|
||||
Some storage services allow downloading the content of a file using a
|
||||
regular http connection, with no authentication. An external special remote
|
||||
for such a storage service can support a readonly mode of operation.
|
||||
|
||||
It works like this:
|
||||
|
||||
* When a key's content is stored on the remote, use SETURLPRESENT to
|
||||
tell git-annex the public url from which it can be downloaded.
|
||||
* When a key's content is removed from the remote, use SETURLMISSING.
|
||||
* Document that this external special remote can be used in readonly mode.
|
||||
|
||||
The user doesn't even need to install your external special remote
|
||||
program to use such a remote! All they need to do is run:
|
||||
`git annex enableremote $remotename readonly=true`
|
||||
|
||||
* The readonly=true parameter makes git-annex download content from the
|
||||
urls recorded earlier by SETURLPRESENT.
|
||||
|
||||
## TODO
|
||||
|
||||
* When storing encrypted files stream the file up/down the pipe, rather
|
||||
|
|
Loading…
Add table
Reference in a new issue