Thank you.  That's just what I needed.

As a side note, the link 
to https://gitlab.com/gitlab-org/gitlab-ce/blob/install/structure.md midway 
down would also be very helpful.

On Tuesday, April 22, 2014 11:49:56 AM UTC-7, Achilleas Pipis wrote:
>
> On 04/22/2014 07:46 PM, Cord Thomas wrote: 
> > Hi, 
> > 
> > We have a GitLab installation with some 150 projects.  The 
> > ./repositories directory consumes ~ 8.1 GB.  I noticed that the ./gitlab 
> > and ./gitlab-satellites directories are also about 9 GB each which 
> > surprised me.  I admittedly do not have a solid understanding of how 
> > gitlab is engineered and the processing that goes on in gitlab/tmp and 
> > gitlab-satellites. 
> > 
> > We are at gitlab 6.5.1. 
> > 
> > Two questions: 
> > 
> > ./gitlab has a tmp/repositories directory which constitutes most of the 
> > 9 GB.  Is this directory needed or can we clean it up?  Are we possibly 
> > missing something in our installation?  would it be safe to run a cron 
> > job to clean up files older than 24 hours or something? 
> > 
>
> Any branch/tag one downloads gets compressed and put into 
> tmp/repositories. You can safely run a cron job and clean it. That's how 
> gitlab.com does it. 
>
> > ./gitlab-satellites have an apparent copies of ./repositories, but 2-3x 
> > the volume of some of the repositories, some smaller.  Is this 
> reasonable? 
> > 
>
> satellites dir is used for forked projects. So if a project is forked 3 
> times, the volume will be x3 :) 
>
> > Is there documentation I can read on this?  I could not find anything. 
> >  I expected it might be in workflow, but that documentation thread 
> > appears to go nowhere. 
> > 
> > Thank you 
> > 
>
> I think you missed that ;) 
>
> https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/architecture.md
>  
>
>
> -- 
> GPG : 0xABF99BE5 
> Blog: http://axilleas.me 
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to