5 ms·
Enterprise says I have to use this unreliable garbage.
by geraldwhen 3y ago
Enterprise says I have to use this unreliable garbage.
- bombolo 3y agoYep. We could self host. But it's forbidden.
- geraldwhen 3y agoWe migrated recently. On prem was never down, but since moving to GitHub were more down than up.
- lol768 3y agoIt's definitely no less reliable than GitLab, where a good 300GB of database data got deleted in production by accident...
- ishanjain28 3y agoAnd how often that has happened? Seems a little harsh
- subtra3t 3y agoJust like calling GitHub "unreliable garbage"...
- ishanjain28 3y agoGithub has been down hundreds of times this year alone. They have reported outages 72 times this year and there are multiple times when services are unavailable and they don't report it on the status page. I don't see how the two situations are comparable
- lol768 3y ago> there are multiple times when services are unavailable and they don't report it on the status page. There's no evidence that the exact same doesn't happen with GitLab. I've had it (consistently) 500 on me in the past when there's nothing on their status page to indicate any issues.
- ishanjain28 3y agoOkay Agreed, Except That's not the point of discussion. I didn't say Gitlab doesn't lie about it or heck, That it doesn't have worse uptime than Github. My argument is that a company erasing 300GB production database once is not a stain on their competency and that it can not be compared to a company which has very frequent outages which also happens to lie when they have outages.
- 8organicbits 3y agogitlab.com or self-hosted?
- hnarn 3y agogitlab.com is implied since it happening on a self-hosted instance would have nothing to do with gitlab as a service (they can't be responsible for your on-site backups). > Trying to restore the replication process, an engineer proceeds to wipe the PostgreSQL database directory, errantly thinking they were doing so on the secondary. Unfortunately this process was executed on the primary instead. The engineer terminated the process a second or two after noticing their mistake, but at this point around 300 GB of data had already been removed. https://about.gitlab.com/blog/2017/02/10/postmortem-of-database-outage-of-january-31/ https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab...
- 8organicbits 3y agoAh I see the link. I'd caution that many people choose between github.com, gitlab.com, and gitlab self-hosted. The reliability of self-hosted gitlab is meaningful, especially when operated competently. People need to know if there are safeguards or foot guns. Backups alone can't prevent data loss.
- namaria 3y agoSubstitute capital expenditure for operating expenses? With interest rates going up? It was already a tough sell with negative real rates...