Basically it comes down to money. I have dual server boxes. Server A has RAID and a partition (3.5 TB) large enough to hold all the repositories I plan. So, it appears that GitLab would be able to handle this with its one git-data dir. Real testing will prove this out.
Server B is a replication box to ensure availability when Server A is in maintenance mode. However Server B has a set of disks, each of which is 2 TB max. I don't have the $ to RAID this up and my belief is that concatenating disks effectively reduces overall reliability. So, in this scenario Server B GitLab can only have a git-data dir of max 2 TB, which is not large enough to mirror my 3.5 TB Server A git-data. Therefore, if GitLab truly cannot address/handle >1 git-data dir, then a solution is to create a second VM on Server B with its own 2 TB partition and its own git-data dir. Then I will have 2 VMs on Server B, each with its own separate git-data dir. Of course this will entail manual management of which repo goes onto which Server B VM, and keeping these synchronized to Server A will require care, but that is a manual process anyway with GitLab CE. Other ideas are certainly welcome; I may be suffering from in the box thinking. On Friday, 29 April 2016 01:14:55 UTC-6, Magnus Therning wrote: > > > Stan Cruise <scru...@gmail.com <javascript:>> writes: > > > Is there a way to have GitLab manage more than a single git-data dir? > > > > A workaround is to run multiple VMs each with a fully independant > > GitLab instance. > > > > Are there any other ideas? > > What's the problem you're trying to solve? > > /M > > -- > Magnus Therning, magnus....@cipherstone.com <javascript:> > Cipherstone Technologies AB > Theres Svenssons gata 10, 417 55 Gothenburg, Sweden > > A distributed system is one in which the failure of a computer you > didn't even know existed can render your own computer unusable. > -- Leslie Lamport > -- 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/afc6bb10-dec4-46b3-a0e9-18654036e222%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
