triadawp.blogg.se - Git annex vs git lfs

GIT ANNEX VS GIT LFS HOW TO

deleting and renaming many times).Īt the end, I had only ~6 GB of MP3 files and ~83 GB in the. Then, I started to classify them in the habitual way (pushing, pulling, merging. I used an external hard disk drive with the main Git repository, and I cloned it into each computer. I had a very similar problem several months ago: ~21 GB of MP3 files, unclassified (bad names, bad id3's, don't know if I like that MP3 file or not.), and replicated on three computers.

If you modify your binary files too often, then I would try to minimize the impact of the huge repository cleaning the history: I would use submodules (as Pat Notz) or two distinct repositories. The program will not work without the files. The files will not change very often (as in years), but they are very relevant to a program. The files are images for a program which generates PDFs with those files in it. What are your experiences/thoughts regarding this?Īlso: Does anybody have experience with multiple Git repositories and managing them in one project? It surely introduces some other things I haven't thought about.

Contra: Removes the simpleness of having the one and only Git repository on the project.

Pro: Checking out/cloning the source code is fast as ever, and the images are properly archived in their own repository.

Contra: Bloats the repository and decreases flexibility to manage the code-base and checkouts, clones, etc.

Pro: Removes the possibility to 'forget' to copy a important file.

Contra: I am strongly against this, as it increases the likelihood of errors when setting up a new site/migrating the old one.

We are currently discussing several alternatives:

GIT ANNEX VS GIT LFS HOW TO

I am looking for opinions of how to handle large binary files on which my source code (web application) is dependent.