There’s a tiny LFS compatibility layer I wrote for isomorphic-git: https://github.com/riboseinc/isogit-lfs.
I found it reasonably straightforward to do the following bare minimum needed for our use case:
Given a blob, perform an appropriate upload request to LFS server, and get LFS pointer metadata as a response.
Serialize received LFS pointer metadata and store it at object’s path in the repository (in place of the original blob).
Parse/deserialize LFS pointer metadata stored at an object’s path.
Given LFS pointer metadata, perform an appropriate download request to LFS server, and receive a blob as response.
Write received blob to a correct LFS cache path in Git directory.
In case of gitui, users would probably expect to be able to check out LFS blobs into working directory, but it wasn’t required in our use case.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4