Loading page
Loading page
Developer tools · GitHub LFS alternative
Store the large files of your Git repositories on your own server, so pushes and CI clones do not eat a metered LFS quota.
LFSX is a Git LFS server. It stores the large binaries of a repository, such as textures, models and video, on your own server. Your Git history stays where it is. You point LFS at LFSX with a .lfsconfig file, and Git LFS works as before.
It is a single small binary with no database. The published image is 4.5 MB compressed. Files are stored on disk by their digest, or in an S3-compatible bucket.
LFSX is for game studios and any team that keeps big binary files in Git. The README gives the example of a 3 GB asset pack cloned by CI ten times a month, which is 30 GB of metered traffic on a hosted forge.
Hosted forges bill LFS storage and bandwidth apart from your plan. With LFSX, that cost becomes the disk on your server. There are no accounts to manage, because LFSX checks access against the upstream repository.
The trade-off: you now own a store of files your team depends on. You look after updates, disk space and backups of the data volume. Remember that git lfs install must run before cloning, or files arrive as small pointer stubs.
Containers: ghcr.io/ferrlabs/lfsx:1.14.1
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose LFSX, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the LFSX setup screen.