I couldn't say what the side effects of sending satellites to /dev/null
would be, but that sounds rather like treating the symptom instead of
fixing the root malady. In other words, once you get those blobs out of
the repo and into Box, you could rebase[1] and let the GC clean up the
unused space.

... That is, if your use case is amenable to rewriting ("losing") the
repo history. Failing that, you can at least save yourself the daily
login by setting a cron job.

Fact is, if your repos are sufficiently large relative to your storage
capacity, you're bound for problems no matter what.

-C

[1]: http://stackoverflow.com/a/9254257/77047

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/14/2014 02:04 PM, Ryan W wrote:
> Chris, do you see any issues arising if I symlinked the satelite-repo
> directory to /dev/null or just changed the perms on it so gitlab
> couldn't write there at all?  No one uses the web ui in any way except
> to maange the permissions on the repositories and grab the git urls when
> they are initially added so we don't need to ever download or merge
> through the web ui but preventing gitlab from cloning repos here would
> allow us to save a few more GB, or at least save me from logging in
> every morning and wiping it :)
> 
> On Tuesday, November 11, 2014 9:20:20 AM UTC-5, chris wrote:
> 
>     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] <javascript:>
>     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] <javascript:>
>     > <mailto:[email protected] <javascript:>>.
>     > 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>
> 
>     >
>     
> <https://groups.google.com/d/msgid/gitlabhq/405b07c6-70c7-4ecb-a3cb-43977164e2ec%40googlegroups.com?utm_medium=email&utm_source=footer
>     
> <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
>     <https://groups.google.com/d/optout>.
> 
> -- 
> 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/e7e7f0de-e269-484d-8b92-8d79f2578638%40googlegroups.com
> <https://groups.google.com/d/msgid/gitlabhq/e7e7f0de-e269-484d-8b92-8d79f2578638%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to