4 ms·
If you want transparent failover you need to use your own domain for the repo URL. In case of a failure you (or some automatic job) would have to change the DNS
by the_duke 6y ago
If you want transparent failover you need to use your own domain for the repo URL. In case of a failure you (or some automatic job) would have to change the DNS record.
Gitlab has a repo mirroring feature [1]. But of course you'd also need to sync users public keys.
Downtimes are so infrequent and relatively short that this isn't worth the effort for me.
You can instead set up a read-only mirror so people can at least still pull and browse the code.. Gitea [2] might be a better choice than Gitlab, since it's much more lightweight and easier to host.
[1] https://docs.gitlab.com/ce/user/project/repository/repository_mirroring.html https://docs.gitlab.com/ce/user/project/repository/repositor...
[2] https://gitea.io https://gitea.io
- tomxor 6y agoThanks this is useful to know > Downtimes are so infrequent and relatively short that this isn't worth the effort for me. That's essentially the same conclusion I keep coming too, occasionally it has hit me when I go to push something but rarely has it blocked me or anyone else from continuing to work. > You can instead set up a read-only mirror so people can at least still pull and browse the code Yeah, this I need to do eventually just for peace of mind as a more automated backup solution. At least I don't have to care about failover.
- mroche 6y agoMaybe some kind of pre/post-push hook to automatically push to a secondary repo? Not entirely sure if this is possible, I’ve never written a Git hook before. https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks