![]() ![]() ![]() And if the images won't be changed that often, then where's the problem? You won't get a big fat delta. Worst case, if you have tons, store them somewhere else or use externals or an extension for binary support. Storing binaries is considered bad practice, yes, but I never worried too much about images. TLDR: if you can, use git-lfs to store images or other binary files in git. git-fat - Another, low-dependency approach.While I appreciate the simplicity my main concern with plugin is that it's fairly unknown and maintained by 1 individual (full disclosure, I am the only other committer at this time and it was for a trivial issue). git-fit - An attempt to create a simpler plugin.git-media - No personal experience with this one.git-annex - This has been around for awhile but frankly it's complexity gets in the way.Only downside is that this is fairly new, so beyond Github there isn't much support, though Gitlab also has support, as does Gitea, and Bitbucket has alluded to support in the future. It's backed by Github and is available on all their repos as of October 2015 and puts the complexity of file management on site storing your repos. git-lfs - While I haven't used this extensively it appears to be the holy grail.This question is pretty old but this is a common question that comes up when dealing with Git and there has some progress on modern solutions to storing large files in a Git repo since the last answer.įor storing large files in Git there are the following projects: I am afraid at $100/terabyte, that excuse is wearing a bit thin. Same applies to any and all binary files that fit the above criteria. I have seen an entire project's original artwork go "poof" when the graphics designer's MacBook hard drive died, all because someone, with infinite wisdom, decided that "binaries don't belong in rev control", and graphics designers (at least this one) don't tend to be good with backups. Why introduce "copy and rename" version control from the dark ages? Put them in your revision control, if they never change, the space penalty is the same as a backup, and they are where you need them.Ĭan they be edited to change the appearance of the software, accidentally or intentionally? Yes - then they MUST be revision controlled somehow, why use another way when you have a perfect solution already. If they are original, they need backing up. Are your images original work or can they be recovered (guaranteed?) from elsewhere? Are they needed to ship a software unit built from source? ![]()
0 Comments
Leave a Reply. |