lunny/git-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ced527048c
git-lfs/docs/api
History
risk danger olson aceb2d2229 write up docs on the basic transfer adapter
2016-11-10 14:47:51 -07:00
..
v1 Add HTTP 507 (Insufficient Storage) to the list of optional statuses (#1473) 2016-08-22 10:37:04 -06:00
v1.3 add object Authenticated property to let servers tell the client to skip the git-credentials check 2016-08-15 16:24:50 -06:00
authentication.md separate the server discovery and auth sections to separate docs 2016-11-10 13:32:47 -07:00
basic-transfers.md write up docs on the basic transfer adapter 2016-11-10 14:47:51 -07:00
batch.md write up docs on the basic transfer adapter 2016-11-10 14:47:51 -07:00
README.md write up docs on the basic transfer adapter 2016-11-10 14:47:51 -07:00
server-discovery.md separate the server discovery and auth sections to separate docs 2016-11-10 13:32:47 -07:00

README.md

Git LFS API

The Git LFS client uses an HTTPS server to coordinate fetching and storing large binary objects separately from a Git server. The basic process the client goes through looks like this:

  1. Discover the LFS Server to use.
  2. Apply Authentication.
  3. Request the Batch API to upload or download objects.
  4. The Batch API's response dictates how the client will transfer the objects.

Current transfer adapters include:

Experimental transfer adapters include: