2 ms·
It's not that I'm against, the contrary, but in the last months I've experienced a physical server crash, a random kernel panic and a failed upgrade of GitLab:
by gregoriol 6y ago
It's not that I'm against, the contrary, but in the last months I've experienced a physical server crash, a random kernel panic and a failed upgrade of GitLab: that all took 10/20 hours of work, didn't result in any data loss, but the downtime was clearly higher than what GitHub has (+ nobody on the team was on holidays at that moment), plus any maintenance like software or system upgrades has to be done outside team working hours to limit the impact.. real self-hosting is not that easy!
- ashildr 6y agoA failed upgrade of GitLab? Can you give details - I got used to monthly Gitlab updates going very smoothly and now I’m a little afraid. What went wrong?
- gregoriol 6y agoLast one we had was because the ssh connection was lost during the apt upgrade (gitlab omnibus ce). Another one I remember was when some new configuration key was needed and prevented one of the components from starting (took ~2 hours to find what it was). It doesn't happen often, don't worry that much though, gitlab omnibus works well, but is hard to investigate/fix because it's huge and not a tech stack we do understand well since we mostly use gitlab-ctl commands, so when something goes wrong it's hard