Towards a production quality open source Git LFS server

about.gitlab.com

28 points·sytse··12 comments

Update from https://github.com/github/git-lfs/issues/584#issuecomment-13... GitHub has no plans to release production ready git-lfs server and suggests we start over, or fork it. GitLab will do the fork as already mentioned in the blog post.

I'll be here in the comments to answer any questions.

What storage backend(s) are you planning to support?

For now just files on disk (NFS block devices) I think. Of course an s3 compatible interface would be cool to have.

Or OpenStack Swift.

Doesn't Swift support the s3 protocol? https://wiki.openstack.org/wiki/Swift/APIFeatureComparison#A... (just like Ceph and others)

More or less; just requesting that if you add S3 support, you use a compatible subset of the API that Swift supports.

OK, thanks.

Since Git LFS support in GitLab is targeted at both CE and EE, do you expect to open up the EE-only git-annex support to CE as well since the two features serve similar purposes?

Edit: "GitLab," not "GibLab," haha.

Thanks for asking. Right now the plan is to keep git-annex EE only. Git Annex can do some neat tricks (multiple storage interfaces, etc.) that Git LFS can't do. But I agree it is not a very congruent situation. We might reconsider when Git LFS is production ready.

This just sounds like whining about having to write an implementation from scratch.

GitHub is free to keep their implementation to themselves. We wanted to prevent a duplication of effort and wanted some context about what to expect. Good thing is this was resolved in https://github.com/github/git-lfs/issues/584

Reply on news.ycombinator.com