git-lfs apiurl parameter
git-lfs: Added an optional apiurl parameter. This needs version 1.2.5 of the haskell git-lfs library to be used. stack.yaml updated to use that. Note that git-annex enableremote can be used to add apiurl= to an existing git-lfs special remote. To allow unsetting the apiurl and instead use the probed url, support enableremote with apiurl set to an empty string. Sponsored-by: Luke T. Shumaker
This commit is contained in:
parent
dcf2f71696
commit
d394f0b020
6 changed files with 95 additions and 29 deletions
|
@ -9,7 +9,7 @@ These parameters can be passed to `git annex initremote` to configure
|
|||
the git-lfs special remote:
|
||||
|
||||
* `url` - Required. The url to the git-lfs repository to use.
|
||||
Can be either a ssh url (scp-style is also accepted) or a http url.
|
||||
Can be either a ssh url (scp-style is also accepted) or a https url.
|
||||
|
||||
* `encryption` - One of "none", "hybrid", "shared", or "pubkey".
|
||||
Required. See [[encryption]]. Also see the encryption notes below.
|
||||
|
@ -18,6 +18,10 @@ the git-lfs special remote:
|
|||
git-annex stores in the repository, as well as to encrypt the git
|
||||
repository itself when using gcrypt.
|
||||
|
||||
* `apiurl` - Optional. The url to the LFS API endpoint. This can be a https
|
||||
or a http url. When this is not specified, or is not set to an url,
|
||||
the API endpoint url is guessed based on the url parameter.
|
||||
|
||||
## efficiency note
|
||||
|
||||
Since git-lfs uses SHA256 checksums, git-annex needs to keep track of the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue