Clever Geek Handbook

What is the advantage of integrating GIT LFS with art

I am trying to use artifactory in my current project. The file storage / management feature with improved Artifactory binaries made me try artifactory. I came across one quirk in the art guide below at the link http://www.jfrog.com/confluence/display/RTF/Git+LFS+Repositories

and I didn't understand what exactly is the advantage of integrating artifactory with GIT LFS, if only GIT can provide a large binary storage function. Can anyone help me understand the benefits of this feature?

+3


source to share


2 answers


Adding to @joran's answer, note that your statement "GIT itself can provide a function for storing large binaries" is not correct. GIT LFS was invented because GIT alone is not very good at handling large binaries. GIT is a version control system that relies heavily on sources being textual and versioned by content.

GIT LFS is a layer that allows you to use familiar GIT commands when managing storage, more suitable for binaries. ATM there are 4 known implementations of such storage, of which Artifactory is the only general purpose storage of artifacts. This means that if you need a repository for any of the other technologies supported by Artifactory, you can use one tool instead of setting up and maintaining a whole zoo of tools for different types of repositories.



I'm with JFrog , the company behind Bintray and [artifactory] , see my profile for more details and links.

+7


source


Git is not suitable for handling versions of large files, mainly because when you clone and checkout such a repo, you will be downloading each version of the file (often wasting time and space, and the problem accumulates for each new version)



0


source






More articles:


All Articles