anybody knows if www.atom.io would be affected by this?
GitHub was down
41–50 of 197 posts
Re: GitHub was down
#42What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Work locally? It's Git.
sure, but if your Build System / CI is based around github, then you are a bit poked.
thank goodness I'm on bitbucket :) One of the things they offer is your own local server synched with their cloud servers for redundancy.
Re: GitHub was down
#43if only we had a decentralized version control system...
Exactly this. It's painful to realize that Git was invented to solve this very problem, but so many use GitHub as their source control server just like CVS and all the other old source control systems.
Then what's the alternative? Push and pull directly from other users who have access to the repository? What if that user is currently offline? There are huge benefits to having a main centralized repo. If you need redundancy for some reason, it's fairly trivial to mirror the repository somewhere else.
Re: GitHub was down
#44Seems like they're saying it's maintenance now? $ gl fatal: remote error: GitHub is offline for maintenance. See http://status.github.com for more info.
That is likely just their standard downtime message.
Only reason I brought it up because it was originally showing the all to familiar unicorn on the website, then it changed to also saying maintenance.
Re: GitHub was down
#45It seems to have been fixed now.
Re: GitHub was down
#46What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Others will say "work locally," but the problem is more in deployment. There's still a lot of app and CI servers out there where the workflow is "push to Github, then some automated script will tell the cluster to pull from Github" rather than "push the changes directly to the cluster." Containerization, especially projects like Kubernetes, make the latter much more viable; your cluster handles its own orchestration and deployment. It's still early days, though, and there's a lot that a new user can get wrong in setting such a system up. Ansible telling servers to git pull from Github may give you better uptime once you factor in your own mistakes.
Re: GitHub was down
#47Re: GitHub was down
#48Earlier quoted context omitted.
Gitlab?
Does anyone know an alternative to githost.io? We don't want to use gitlab.org as it's painfully slow but also don't want to manage our own gitlab instance. edit: We don't like the recent changes made in githost. ( Replaced the $35 option with $149 ) We're a team of 15 people. edit2: should have clarified; I'm hooked to GitLab, just looking for another service that does managed hosting. Not looking for GitLab alterna…
Gitlab.com? BitBucket is the other major player that comes to mind, but googling "hosting git" returns enough results to melt ones mind.
If you're really concerned, you run it yourself. GitLab insider a docker container isn't hard to manage. You can even 1-click Gitlab onto a DO Droplet in just a few minutes: https://www.digitalocean.com/community/tutorials/how-to-use-...
Re: GitHub was down
#49if only we had a decentralized version control system...
it's not about github though, it's about how people use git. nothing stops one from keeping a mirror, just in case similar situations happen
Re: GitHub was down
#50What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
A common solution is to decide that github is down rarely enough that this isn't a problem. Eg if your only dependency on github is at deploy time, it might be ok if you can't deploy for a few hours a year when github is down. If you have a bigger (eg runtime) dependency or if being unable to deploy for a few hours is a problem, then yes– you run your own git server.