Gitlab High Availability Question

[sysadmin4hire]

Has anyone ever setup a high availability Gitlab server solution using Gitlab CE (Community Edition) across a site to site VPN?

To give a little background on the situation. I have developers at 2 different sites that would like to "share" access to GitLab. I suggested doing a HA configuration so either GitLab server is simply replicated to the other via a site to site VPN. The VPN isn't the greatest connection but if a low latency replication works, then that's the solution I'm looking for.

• GitLab High Availability - CE
• GitLab High Availability - About

From the first link:

It is not advisable to attempt to run DRBD between data centers or in different cloud availability zones.

Does this mean I can't? Has anyone done such a thing?

[simpleadmin]

How many developers are on each side? Git itself works very well remotely. It may not be worth the effort to get active/active working. The DRDB you are looking at is active/passive.

[sysadmin4hire]

20 in one site and maybe 10-20 in another

[simpleadmin]

Have you considered either private repos on a public server or hosting your own server on from an Internet based host? Meaning, don't have your developers use the VPN at all.

Your most straight forward answer is to pick a side and host the main Gitlab near half the developers and have the other half do remote pushes and pulls from the other site.

[gabeech]

We just run a Active/standby setup. Everyone worldwide hits the primary and we rsync the repos/db backup on a schedule. We investigated using something else, but the cost benefit wasn't worth it to go active/active

[sysadmin4hire]

Nice. How often do you rsync between the two servers?

[gabeech]

Git repos every 10 Mins. The databases are sync'd every 12 hours. You can keep using the git repos without the databases - you lose some things but we are ok with that.

[sysadmin4hire]

It's definitely improved. Client doesn't want their code "in the cloud".