Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

version control on large files

We happily use SVN for SCM at work. Currently I've got our binary assets in the same SVN repository as our code. SVN supports very large files (it transmits them 'streamily' to keep memory usage sane), but it is SLOOWWWWW.

What asset management software do you recommend, for about a GB (and growing) worth of assets? We would prefer branching and merging (different assets & config files go to different customers).

like image 451
Dustin Getz Avatar asked Nov 08 '08 20:11

Dustin Getz


People also ask

What are the three types of version control?

The types of VCS are: Local Version Control System. Centralized Version Control System. Distributed Version Control System.

Can Git handle large binary files?

Git LFS is a Git extension used to manage large files and binary files in a separate Git repository. Most projects today have both code and binary assets. And storing large binary files in Git repositories can be a bottleneck for Git users. That's why some Git users add Git Large File Storage (LFS).

Why is version control a problem?

The version control system can often merge changes that different people made simultaneously. However, when two people edit the same line, then this is a conflict that a person must manually resolve. To avoid this tedious, error-prone work, you should strive to avoid conflicts.


2 Answers

Please be very aware that it is almost impossible to merge binary files! At least automatically. At least I've never heard of a program that supports three-way merging on a binary format. Let alone conflict resolving.

That's why most asset management tools don't have branching, since it makes little sense since you can't merge again. Locking and linear history is better. If you want to "branch", then make a copy of the file with history.

like image 60
Hugo Avatar answered Oct 13 '22 02:10

Hugo


At my company, we use Documentum as a ECMS, managing lots (and I mean really lots) of binary files. Documentum (or other ECMS like Alfresco) are supposed to be the "right" solution to manage documents. Documentum supprots tagging and branching, and can expose files as WebDAV (so integration into your workflow can be more or lessa transparent).

That's the theory. In practice, we found Documentum slow, hard to configure and manage. And honestly, even if we have lots of documents, most of them are not larger than a few 100's Mo.

This answer more of what you should not do than what you should do ... sorry ...

like image 23
Guillaume Avatar answered Oct 13 '22 03:10

Guillaume