Re:Incident with GitHub Packages and GitHub Pages
by dahfizz on Monday April 25, 2022 @07:52AM
(#31153231)
This is like the third downtime in a month. Hosting your own infra is easier than people think, but it is completely trivial if weekly downtime is the expectation.
Re:Incident with GitHub Packages and GitHub Pages
by Helitioo on Monday April 25, 2022 @11:51AM
(#31156594)
I have been on both sides.
GitHub downtime is something I can just tell managment and prepare things to put it out of high critical path.
Like I would not pull images from GitHub on my k8s cluster.
Gitlab works absolutely but you know I don't want to do gitlab updates, do backup, do regular backup/restore test, deleting backups etc.
I prefer to create new things.
Re:Incident with GitHub Packages and GitHub Pages
by dncornholio on Monday April 25, 2022 @09:01AM
(#31153861)
Maintaining gitlab has been nothing more than sudo apt-get update && sudo apt-get install gitlab-ee.
Their releases often have security vulnerabilities though. But other than that, even the community edition is packed with features, it's a no brainer for me ;)
Re:Incident with GitHub Packages and GitHub Pages
by Helitioo on Monday April 25, 2022 @11:53AM
(#31156637)
The security issues in the last year were shocking to me.
You also need to do backups, try restore, you might need to announce a maintenance window.
And for what? Getting stress from mgmnt when it breaks? With a GitHub downtime that's just it. No one cares, everyone accepts it as given.
Re:Incident with GitHub Packages and GitHub Pages
by mac-chaffee on Monday April 25, 2022 @12:08PM
(#31156860)
Agreed. The people saying self-hosting is easy would do well to read this: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/RunningSer...
GitHub is still a no brainer for me.