I'm looking for a way (a tool?) to enrich a git repository with binary blobs (e.g.external dependency jars, db seeds). Team members need the blobs to start the dev env, but the files are too large to be committed to git, especially if they change over time. What to do? I'm thinking ...: - sync files from Google Cloud Storage (or S3) - config file committed to git only holds pointers to current versions (hashes?) - it's fine to require developers to run bin/sync-blobs manually occasionally - limit tooling complexity. I've had bad experiences with git-lfs and git-annex, but happy to hear about reports to the contrary. Is there anything fitting this profile out there? Or am I missing any simple solutions?

the external dependency jars can go on a maven repository

if you can somehow wrap the db seeds into an maven artifact you can upload them there as well

then you can just create dependencies in leiningen onto them

or boot

and it will download them

@jgeraert an interesting idea, but not sure if storing a 100M db dump file in a jar is ideal

but I'll think about it. any suggestion for simple private maven hosting?

>- config file committed to git only holds pointers to current versions (hashes?) vote for this, for it's the simplest possible solution, AFAICS >- it's fine to require developers to run bin/sync-blobs manually occasionally why don't use git hooks instead?

im sure there's a library specifically for managing binary data in git... let me try and find it

found it: https://github.com/git-lfs/git-lfs

>- limit tooling complexity. I've had bad experiences with git-lfs and git-annex, but happy to hear about reports to the contrary.

oh woops

my bad

@pesterhazy you can also create a simple repository on s3

@pesterhazy see http://www.yegor256.com/2015/09/07/maven-repository-amazon-s3.html

@sundarj like I said I tried it but found it horribly slow (with github's servers) and github's plan is way too expensive

what about having a git subtree / submodule purely for binary files?

@sundarj that still requires you to keep old versions around (in .git) essentially forever, no?

right

@jgeraert http://s3auth.com is very interesting

I guess you have to trust the people behind http://s3auth.com?

it's open source, i suppose you could roll your own

https://github.com/yegor256/s3auth

hm all very interesting

and of course there is nexus/artifactory/archiva

but you need to host that yourself too ofc

s3auth seems dangerous (uses HTTP Basic Auth without encryption)