4 ms·
The only lesson to be learned here, one that needs to be repeated time and time again: Don't put all your eggs into one basket.
by gridlockd 7y ago
The only lesson to be learned here, one that needs to be repeated time and time again:
Don't put all your eggs into one basket.
- bsder 7y agoThe lesson to be learned here is "Don't use GitHub." Use something that you can run your own instance of (like GitLab) and make the cloud version a shadow copy of your local one. That way if they pull the rug out from under you, you actually have some way of dealing with the issue.
- unixhero 7y agoDon't put all your projects in one cloud And... Use Gitlab
- majkinetor 7y agoGitlab too had incidents, remember db backup fiasco ? I know few devs that lost issues and wikis that day. Just backup your repos once a year, lets not be paranoid.
- unixhero 7y agoYeah sure. But since Gitlab is possible to run self-hosted, you can back up the entire instance from the public cloud to the self-hosted version. That's pretty great.
- majkinetor 7y agoBy the same logic you can have a script that does git pull locally as cron job all the time along with exporting issues (wikis are just another implicit repo). The point was that nobody does that for backup purposes in advance, and maintaining local Gitlab along with supportive infrastructure is not trivial task.
- antisemiotic 7y agoIn case of GitLab, the incident was caused by a human error, and they worked hard to fix it afterwards. GitHub and DigitalOcean (to name the ones recently mentioned on HN) have delibrately set up automated kill switches with no possibility of appeal, sans crying on Twitter. Sure, when data is lost then it may not matter in the end, but I'm still more sympathetic to the former.
- majkinetor 7y agoIndeed, how GitLab handled the incident was exemplary. That is entirely different topic.
- dsumenkovic 7y agoHere's the blog post about it https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/ https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...
- oakslab 7y agoThat's why I set up my github and gitlab to mirror each other. gitlab can even automatically get the latest changes from my github repo. too bad github can't do this yet [1]. [1]: https://github.com/isaacs/github/issues/415 https://github.com/isaacs/github/issues/415
- ernsheong 7y agoPut another way, do not treat Github/lab/Bitbucket as file hosting. As a repository it's fine, because it is assumed you have a local copy.