3 ms·
I did a quick check, but I'm not an expert. Make one the main and the backup in readonly. https://docs.gitlab.com/ee/administration/read_only_gitlab.html http
by NicoJuicy 5y ago
I did a quick check, but I'm not an expert.
Make one the main and the backup in readonly.
https://docs.gitlab.com/ee/administration/read_only_gitlab.html https://docs.gitlab.com/ee/administration/read_only_gitlab.h...
You can stop the readonly from doing CI.
Do a healthcheck on the main repo and let a gateway in front it.
If the main is down, undo the readonly access.
I'm not 100% sure what to do when the main goes backup though.
That aside, I'm not sure if you want this. What duration/year was a downtime on the datacenter blocking deployments/coding?
- __warlord__ 5y ago> I'm not 100% sure what to do when the main goes backup though. I'm wondering this as well, it becomes very cumbersome to bring both instances at the same data consistency without a third party (like a queue)
- NicoJuicy 5y agoI don't think a queue is possible concerning commits. This could be part of the solution though. But automating everything seems not worth the effort. https://docs.gitlab.com/ee/administration/geo/disaster_recovery/ https://docs.gitlab.com/ee/administration/geo/disaster_recov...