3 ms·
The "filter-by-filetype" approach used here is going to work a lot better for mixed-content repositories than git-annex, which doesn't have that capability buil
by jewel 12y ago
The "filter-by-filetype" approach used here is going to work a lot better for mixed-content repositories than git-annex, which doesn't have that capability built-in (to my knowledge).
git-annex has been great for my photo collection (which is strictly binary files). It lets me keep a partial checkout of photos on my laptop and desktop, while replicating the backup to multiple hosts around the internet.
At work we have a bunch of video themes that are partially XML and INI files and partially JPG and MP4. LFS would work great for us, except we don't use github (we don't have a need for it.) It looks like this is going to be very simple for that kind of workflow.
Just yesterday HN user dangero was looking for this exact sort of thing, large file support in git that didn't add too much complexity to the workflow: https://news.ycombinator.com/item?id=9330125 https://news.ycombinator.com/item?id=9330125
- icebraining 12y agoThe filter-by-filetype can be replace by small script that augments git: http://git-annex.branchable.com/forum/help_running_git-annex_on_top_of_existing_repo/#comment-41049e5e5de08f6cc0b76f9298b8e4c0 http://git-annex.branchable.com/forum/help_running_git-annex...
- sytse 12y agoWould be nice to replace that with git hooks so you can just use regular git commands. Any idea's if that is feasible?
- icebraining 12y agoI'm not sure, but I doubt a hook would do. An alternative would be to have a frontend script to git that would shadow the git command (using shell aliases) and call git-annex when appropriate.
- sytse 12y agoYeah, I don't like shell aliases but it would work. I wonder how the LFS client works.
- joeyh 12y agoYou don't need a script; git-annex has the same capability, although configured differently. For example: git config annex.largefiles "*.mp3 or *.mp4 or *.jpg or largerthan(100kb)" git annex add .