I tried the pull/push method and it works fine. It will be quite manual hence a script/cron is in order for sure, especially since I plan to have many repos.
A related question: My current idea/plan is to host a set of repos managed via GitLab that will likely approach a 3 TB size, all stored on a RAID (GitLab will run on a VM on this box). The hardware is all tried and true and currently hosting shares. Then I may mirror all these repos to a second VM on a second server box, for availability purposes. Hence my previous mirroring questions. The problem is that the secondary server is not RAIDed and the disks are separate and therefore a non-contiguous fs. I realize I can simple throw more money at it and RAID it exactly like the primary server, but money is an issue. With non-continuous storage I can distribute the repos over the disks, but I understand that GitLab only can address a single data dir for its repo storage. I also don't want to mount disks on disks, given the added reliability issues. The questions become: > Is there a way to have GitLab manage more than a single git-data dir? Thus allowing storage across separate disks. > I have seen posts re having >1 instance of GitLab on a pc, but it sounds more trouble than one wants. >> One clear option to me is to run a second GitLab on a second VM. Simple, clean, separate. Comments? On Sunday, 24 April 2016 13:31:09 UTC-6, Jeroen de Neef wrote: > > Hey Stan, > > You could make a cronjob to automatically pull new changes and to push > them, however that would give you no indication if there is a merge failure. > > As I have said before, I'd like mirroring in CE as well. I'd use it in an > instant for the Upstreams! > > Kind regards, > > Jeroen > > 2016-04-24 21:27 GMT+02:00 Stan Cruise <scru...@gmail.com <javascript:>>: > >> Yes, I see that now! Many thanks for your detailed response to my trivial >> question. >> >> I will proceed to manually manage a solution. >> >> Stan >> >> >> On Sunday, 24 April 2016 13:21:01 UTC-6, Jeroen de Neef wrote: >>> >>> Hi Stan, >>> >>> It looks like the image shows that it is a mirror of the Community >>> Edition repository. >>> The screenshot does not indicate on which type of installation the >>> mirror runs. >>> >>> When you look at the URL of the documentation, it appears that it is >>> documentation directed towards Enterprise Edition. >>> http://doc.gitlab.com/*ee*/workflow/repository_mirroring.html >>> >>> Kind regards, >>> >>> Jeroen >>> >>> 2016-04-24 20:46 GMT+02:00 Stan Cruise <scru...@gmail.com>: >>> >>>> Thanks for the quick reply. >>>> >>>> I suspected that, however the documentation shows "GitLab Community >>>> Edition" in the screenshot: >>>> >>>> http://doc.gitlab.com/ee/workflow/repository_mirroring.htm >>>> <http://www.google.com/url?q=http%3A%2F%2Fdoc.gitlab.com%2Fee%2Fworkflow%2Frepository_mirroring.html&sa=D&sntz=1&usg=AFQjCNG7eMzTv0v3E5TJz71ZIOGByNQSmw> >>>> >>>> >>>> Just a documentation bug? >>>> >>>> >>>> On Sunday, 24 April 2016 12:28:11 UTC-6, Jeroen de Neef wrote: >>>>> >>>>> Hello Stan, >>>>> >>>>> Repository Mirroring is a GitLab EE feature only as far as I know. >>>>> https://about.gitlab.com/2016/04/22/gitlab-8-7-released/ >>>>> Personally I'd love to have it for CE as well, it would make keeping >>>>> up-to-date with upstream easier. >>>>> >>>>> Kind regards, >>>>> >>>>> Jeroen >>>>> >>>>> 2016-04-24 20:23 GMT+02:00 Stan Cruise <scru...@gmail.com>: >>>>> >>>>>> http://doc.gitlab.com/ee/workflow/repository_mirroring.html >>>>>> <http://www.google.com/url?q=http%3A%2F%2Fdoc.gitlab.com%2Fee%2Fworkflow%2Frepository_mirroring.html&sa=D&sntz=1&usg=AFQjCNG7eMzTv0v3E5TJz71ZIOGByNQSmw> >>>>>> >>>>>> The documentation at the above link indicates that one can mirror an >>>>>> existing project by going to the Project Settings and selecting >>>>>> Repository >>>>>> Mirroring. >>>>>> >>>>>> This option does not exist on my installation. >>>>>> >>>>>> gitlab-ce 8.6.7 ce.0.el7 >>>>>> >>>>>> Is there some conf setting I require? Is this available on the >>>>>> omnibus install? >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Stan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> 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+u...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/gitlabhq/3606cfa2-8975-444e-bcac-b9959f1323de%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/gitlabhq/3606cfa2-8975-444e-bcac-b9959f1323de%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit 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 gitlabhq+u...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/gitlabhq/055c2c37-d3ac-46de-88cb-3669ed37d973%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/gitlabhq/055c2c37-d3ac-46de-88cb-3669ed37d973%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit 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 gitlabhq+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/c349a0f0-b7ab-4603-9911-e82faba42987%40googlegroups.com >> >> <https://groups.google.com/d/msgid/gitlabhq/c349a0f0-b7ab-4603-9911-e82faba42987%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit 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 gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/aeb6f6f0-c1d4-4d72-8694-6ae85efe7640%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
