If these large binary artifacts are derived data, I wouldn't keep them in the repository at all. If they are semi-transient data (say, recent builds) I might consider a script to push them on S3 or similar with a reasonable expiry.
Otherwise... if it's in the repo... it's on the disk for Gitlab. And assuming these assets are not compressible, you're out of luck. Chris Tonkinson Forge Software [email protected] 800.875.3048 x1 "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." -Antoine de Saint-Exupery On 11/11/2014 07:32 AM, Ryan W wrote: > In the same vein as my previous post I was curious if you guys could > share some strategies to keep the disk usage to a minimum? We host git > repo's that contain a lot of large binary files and while I've read that > git-annex would be a great solution however it doesn't seem to be > supported with gitlab so that's a no go :( I've read a bit about > git-prune so that's on my radar but anything else you guys could > recommend would be most appreciated. > > thanks! > > -- > You received this message because you are subscribed to the Google > Groups "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/405b07c6-70c7-4ecb-a3cb-43977164e2ec%40googlegroups.com > <https://groups.google.com/d/msgid/gitlabhq/405b07c6-70c7-4ecb-a3cb-43977164e2ec%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
