serial-port-json-server Consider not putting binaries in git

Trying to clone this repo, I was surprised by the size of it. It seems the binaries are included in the repo, making the repo big quickly.

Putting binaries in a git repo isn't generally recommended. Since every clone fetches the entire repo (and git can't really efficiently compress binaries), the repo size will quickly grow, making it harder to work with.

Perhaps you should consider removing the binaries (and pruning the history of them)?

Just FYI, feel free to close this issue if you feel otherwise.

Nov 25 '14 17:11 matthijskooijman

I agree with you. Sadly I have to compile this on an Ubuntu Virtual Machine to cross-compile for all platforms at once. The only easy way to get those final binaries over to Google App Engine is from Github. Just haven't had time to do any workarounds. One of these days I'll get the binaries the heck out of this repo.

Nov 26 '14 00:11 johnlauer

Perhaps using a separate repo just for the binaries makes sense? Or you could create a "release" in github through the webui, you can attach binary files to a release (which is intended for exactly this I think).

Nov 26 '14 06:11 matthijskooijman

Or write up a pom and push it out to maven or another repo

Dec 28 '14 21:12 DanielJoyce

Yeah, I'll figure out a better way for the cross-compiling script to not use Github as it's transfer method. Just removed v1.75 snapshots just now to lighten up the repo.

Dec 28 '14 21:12 johnlauer

FWIW, I don't think removing stuff lightens the repo, a clone will always get the entire repo including history. To really fix this, you'd have to git filter-branch (IIRC) to remove them from the history, which breaks fast-forwarding on existing clones...

Dec 29 '14 11:12 matthijskooijman

A couple months ago I did run a filter to remove the binaries, so the repo is/should be lighter now.

May 28 '15 16:05 johnlauer