Blog Company Towards a production quality open source Git LFS server
Published on: August 13, 2015
3 min read

Towards a production quality open source Git LFS server

At GitLab we would love to be compatible with Git Large File Support (LFS).



Since GitLab 8.2 we supports Git LFS in GitLab CE and EE.

Original article

At GitLab we would love to be compatible with Git Large File Support (LFS). We plan to base our implementation on a reference implementation that is currently not in a production ready state. But we hope that over time we can get to production level support. What follows is some background how and why we are taking this path instead of reusing an existing solution.

Git repositories can't get larger than a few gigabytes so if you want to use large binaries you need to extend it. The most extensive open source project to do this is Git Annex, which started in 2010. There were many other projects similar to this such as Git Media. GitHub chose to start a new project in private called Git LFS in September 2013 based on Git Media.

In February of 2015 we released support for Git Annex in our proprietary GitLab Enterprise Edition. Almost all of the code to support this was included in the open source GitLab Shell.

In April of 2015 GitHub announced Git LFS and open sourced the client and a reference implementation for the server. The reference implementation is called 'lfs-test-server' and the first section of the readme mentions that "It is intended to be used for testing the Git LFS client and is not in a production ready state." The client implementation is really well done and many people request support for it on our feature request tracker.

Obviously we would like to support it properly and wondered if the test server code is something we can use in production. We did not get a response to the above tweet nor to an email we sent. Of course nobody owes us a response and GitHub is free to do as they please with their code.

Interestingly a day later the twitter account gitlabceohere is also in the market for something production-ready. We don't know who is behind the account (which has been pretty funny so far), we only know that the first 6 followers of the account are all current or former GitHub employees.

We think that the best course of action is to use the Git LFS reference implementation and make it work for GitLab. Unfortunately we'll have to fork the project since we have to remove the user management that is included in the project. Of course our fork will be open source and in addition we plan to add Git LFS support to both GitLab CE and EE. The work on this has already started with that was contributed by Artem Navrotskiy. Hopefully there will be more merge requests from the rest of the community and the people at GitLab the company will do their best to contribute too. Currently our estimate is to release an alpha version of Git LFS with GitLab 8.1 and a beta in 8.2.

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

New to GitLab and not sure where to start?

Get started guide

Learn about what GitLab can do for your team

Talk to an expert