Taking this one step further, keeping in mind that we use the web interface solely for repo creation, access admin and the wiki, would there be any major problems with changing the perms on the satellite directory so that nothing could be written there in the future? Or just symlinking it to /dev/null so that gitlabs would think it's writing just fine but it would all just go into oblivion instead of bloating the drive?
On Tuesday, November 11, 2014 7:29:37 AM UTC-5, Ryan W wrote: > > In an attempt to reduce the footprint that gitlab is taking up on our > instance I was wondering if there are any potential issues for wiping the > satellite repo directory? I've read that it should be treated as a temp > directory but I wanted to check to make sure that wiping it on a regular > basis isn't going to cause issues with Gitlab. > > In the same line of thinking, can anyone think of any reasons not to setup > a nightly cron that wipes it every night at 3am or something? There isn't > a lot of merging going on at all on our server, maybe once a week we'll > merge branches and definitely not at 3am :) > > Thanks in advance for your help! > -- 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 gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/90006d6c-5e3d-4947-88f4-a834b7c98c66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
