Stop waiting for LFS locks. Start shipping faster. [GitHub Repository Link] Try it now: docker pull ghcr.io/lfs-rev-bouncer/latest
git config lfs.url "http://localhost:8080" That’s it. The Bouncer will transparently proxy, cache, and optimize every LFS operation. Git LFS was never designed for the parallel, high-throughput world of modern CI/CD. LFS Rev Bouncer fixes that without changing a single line of your existing code. lfs rev bouncer
Enter the – the missing link between your CI/CD pipeline and your Git LFS server. What is LFS Rev Bouncer? Think of it as a smart traffic cop for your LFS objects. By default, Git LFS locks files during transfer, causing massive queue times when multiple runners or developers try to push large assets simultaneously. The "Rev Bouncer" intercepts these requests, validates revisions, and allows parallel processing without corrupting your pointers. The Problem It Solves We’ve all seen it: Stop waiting for LFS locks
Title: Breaking the Bottleneck: Why LFS Rev Bouncer is a Game-Changer for High-Stakes Workflows The Bouncer will transparently proxy, cache, and optimize
If you’ve ever worked with large files in Git (binaries, datasets, or release artifacts), you know the pain. Git LFS (Large File Storage) solved the storage problem, but it introduced a new one: .
# Docker quickstart docker run -p 8080:8080 \ -e LFS_BOUNCER_BACKEND="https://your-lfs-server.com" \ -e LFS_BOUNCER_REDIS="redis://cache:6379" \ ghcr.io/lfs-rev-bouncer/latest Then configure your clients:
Have you hit LFS concurrency limits in production? Drop a comment below – we’d love to hear your horror stories.