4 ms·

Git excels at tracking human keyboard output. A productive developer might write 100KB of code annually so a git repo can represent many developer years of col

Git excels at tracking human keyboard output. A productive developer might write 100KB of code annually so a git repo can represent many developer years of collaborative effort in just a few MB. That is, unless you require git to track large media files, third party BLOBs, or build output. However, sometimes tracking these things are necessary, and since there isn't an obvious companion technology to git for caching large media assets ("blob hub?") or tracking historical build output ("release hub?"), devs abuse git itself. I wish there were a widely accepted stack that would make it easy to keep the source in the source repo, and track the multi-gb blobs by reference.

foepys 4y ago
You mean something like git Large File Storage? It comes with git for Windows by default and every Linux distro I know has it in its repos. MacOS also has it in Homebrew. https://git-lfs.github.com/ https://git-lfs.github.com/ It's basically one click/command away.
WorldMaker 4y ago
Git LFS is a pretty widely accepted stack for managing binary blobs by reference in git: https://git-lfs.github.com/ https://git-lfs.github.com/ The plugin is installed out of the box in many git distributions now. Many hosts support it today, including Gitlab, which is relevant to this article's discussion: https://docs.gitlab.com/ee/topics/git/lfs/ https://docs.gitlab.com/ee/topics/git/lfs/
- Dayshine 4y ago
  I have yet to find a host that has at all usable Git LFS pricing though. GitLab is $60/m (edit, per year? unclear in pricing page) for 10GB storage and 20GB/m transfer. So, I can checkout my repo twice a month!? GitHub is similar, with a 1:1 ratio for storage and transfer. So you can checkout your repo once a month.
adobrawy 4y ago
> companion technology to git for caching large media assets ("blob hub?") or There is Amazon S3 or any other cloud storage. > tracking historical build output ("release hub?") There are OCI artifact registries. For me, there is rather issue that when all you have is a hammer, everything looks like a nail.

foepys 4y ago

You mean something like git Large File Storage? It comes with git for Windows by default and every Linux distro I know has it in its repos. MacOS also has it in Homebrew. https://git-lfs.github.com/ https://git-lfs.github.com/ It's basically one click/command away.

WorldMaker 4y ago

Git LFS is a pretty widely accepted stack for managing binary blobs by reference in git: https://git-lfs.github.com/ https://git-lfs.github.com/ The plugin is installed out of the box in many git distributions now. Many hosts support it today, including Gitlab, which is relevant to this article's discussion: https://docs.gitlab.com/ee/topics/git/lfs/ https://docs.gitlab.com/ee/topics/git/lfs/

Dayshine 4y ago
I have yet to find a host that has at all usable Git LFS pricing though. GitLab is $60/m (edit, per year? unclear in pricing page) for 10GB storage and 20GB/m transfer. So, I can checkout my repo twice a month!? GitHub is similar, with a 1:1 ratio for storage and transfer. So you can checkout your repo once a month.

adobrawy 4y ago

> companion technology to git for caching large media assets ("blob hub?") or There is Amazon S3 or any other cloud storage. > tracking historical build output ("release hub?") There are OCI artifact registries. For me, there is rather issue that when all you have is a hammer, everything looks like a nail.