Git LFS

Finluth implements the Git LFS basic transfer adapter for authenticated repositories. LFS object data is stored separately from Git objects in .finluth/lfs-objects and is included in the existing encrypted data-directory backup.

The default per-object upload limit is 2 GiB; set LFS_MAX_OBJECT_BYTES in .env to a different positive byte limit (minimum 1 KiB). Ensure the reverse proxy accepts request bodies at least this large and that the persistent volume has enough space. There is no per-repository storage quota yet.

Track files

Install Git LFS on the client, run git lfs install, then git lfs track '*.psd' (or another pattern), commit the generated .gitattributes, and push normally. Git LFS uses the same Finluth Git access token as Git push/fetch.

GitHub mirror transfers

GitHub ref sync transfers Git history and LFS pointer files, but it does not transfer LFS payloads. Before cutover, the migration checklist scans LFS pointers across all commits reachable from repository refs and checks that each payload exists in Finluth with the expected size and SHA-256. Cutover is blocked while any payload is missing or fails integrity checks.

Transfer the payloads while the GitHub mirror is still linked. Git ref pushes remain disabled during mirroring, but repository writers can upload and verify LFS payloads:

git lfs fetch --all origin
git lfs push --all finluth

After the transfer, refresh the migration checklist and confirm the LFS row is complete. LFS payload bytes are not scanned by Finluth's Git-history secret scanner; the scanner sees only the small pointer files committed to Git.