> [...] programmers asking why git has problems with their newly requested LFS and a 40gb video file they decided to store.
The thing is, git, as our industry uses it, is not really a good tool for
keeping artifacts, and "video" sounds like an artifact, not a source file.
I'd like to see more artifact repositories, especially the ones that you can
talk to from command line or from a Python/Ruby/whatever script. I haven't
found any such thing, so I wrote my own.
As severine found out, it's called GrailBag
(https://github.com/dozzie/grailbag). Docs and README are lacking, to put it
mildly, so I don't deem it ready for being published, but I don't exactly hide
it either.
From the features, GrailBag stores files along with key:value pairs as
metadata (not surprising), has a command line client to
list/modify/upload/download/delete the artifacts, and has a Python module for
doing the same from a more sophisticated script.
Additionally there is an interpreter of a simple language that describes
directory tree where artifacts will be deployed (which artifacts to download,
how to name the files, what directories and symlinks to create). This way you
can write a cron script that deploys whatever you have in the repository, e.g.
in a cold-standby server scenario (two servers having the same configuration,
but one shut down and only powered on when the first one fails; on the first
run of the cron task, the spare server downloads all the missing files,
including whatever got stored while the server was shut down).
The thing is, git, as our industry uses it, is not really a good tool for keeping artifacts, and "video" sounds like an artifact, not a source file. I'd like to see more artifact repositories, especially the ones that you can talk to from command line or from a Python/Ruby/whatever script. I haven't found any such thing, so I wrote my own.