4 ms·

Github is just a node. IF Github dies , people still have the full repos on their computers.That's not always the case with SVN... And most people are too lazy/

by camus 13y ago

Github is just a node. IF Github dies , people still have the full repos on their computers.That's not always the case with SVN... And most people are too lazy/dont have resources to set up a git server anyway.

__alexs 13y ago
Most teams that work on GitHub have none of their own workflow or infrastructure for sharing code when GH goes down. You can probably blame those teams for that more than GitHub but people do seem to have bought into the idea that we can just jam everything up to GitHub and get it back later.
- briandear 13y ago
  Of course from a risk-management perspective, the likelihood of a long term outage is statistically low enough to not justify the expenditure for setting up and maintaining alternative systems (other than simply having repos backed up.) It's the anti-TSA approach. The TSA spends billions and hassles everyone despite the relative rareness of air-travel attacks. But, the severity of a potential attack weighed against the expenditure has led politicians to believe that the cost is worth it. The Heroku/AWS outages a few years back had far more of an impact, yet Heroku still (to my knowledge) relies exclusively on AWS-East, because presumably the risk-profile doesn't exceed the threshold to justify the expenditures required to mitigate the risk. I just wish the attackers would be considerate enough to share the schedule for these attacks ahead of time, so I can plan a longer lunch. The rudeness of these attackers is unparalleled. I'm inclined to write them a strongly worded letter suggesting same.
regularfry 13y ago
If your workflow involves tickets on github, you're going to have a bad time.
- tnorthcutt 13y ago
  If your workflow involves [thing] on [service], you're going to have a bad time.
jlarocco 13y ago
The problem isn't developer access to the code, but that GitHub gets tightly linked to other tools, such as continuous integration and test tools. If Jenkins is expecting to pull the latest code from GitHub, but GitHub is down it's a PITA. There's also stuff like GitHub Issues, which are separate from the actual Git hosting. So even if the source code is available and the 3rd party tools aren't broken, work can still be interrupted.
edavis 13y ago
This is true but it misses the point of Github. Nobody denies your blobs are safe and available elsewhere when Github goes down. It's the infrastructure around those blobs that makes Github so popular. It's your issues and pull requests, your wiki, your connection to Travis-CI that are gone when Github goes down. That is why people get angry when it goes down.
nilved 13y ago
What's a "git server?" Set up any machine that can be SSHed into, maybe apt-get install git and you're done. Git is just files.

by camus 13y ago

__alexs 13y ago

Most teams that work on GitHub have none of their own workflow or infrastructure for sharing code when GH goes down. You can probably blame those teams for that more than GitHub but people do seem to have bought into the idea that we can just jam everything up to GitHub and get it back later.

briandear 13y ago
Of course from a risk-management perspective, the likelihood of a long term outage is statistically low enough to not justify the expenditure for setting up and maintaining alternative systems (other than simply having repos backed up.) It's the anti-TSA approach. The TSA spends billions and hassles everyone despite the relative rareness of air-travel attacks. But, the severity of a potential attack weighed against the expenditure has led politicians to believe that the cost is worth it. The Heroku/AWS outages a few years back had far more of an impact, yet Heroku still (to my knowledge) relies exclusively on AWS-East, because presumably the risk-profile doesn't exceed the threshold to justify the expenditures required to mitigate the risk. I just wish the attackers would be considerate enough to share the schedule for these attacks ahead of time, so I can plan a longer lunch. The rudeness of these attackers is unparalleled. I'm inclined to write them a strongly worded letter suggesting same.

regularfry 13y ago

If your workflow involves tickets on github, you're going to have a bad time.

tnorthcutt 13y ago
If your workflow involves [thing] on [service], you're going to have a bad time.

jlarocco 13y ago

The problem isn't developer access to the code, but that GitHub gets tightly linked to other tools, such as continuous integration and test tools. If Jenkins is expecting to pull the latest code from GitHub, but GitHub is down it's a PITA. There's also stuff like GitHub Issues, which are separate from the actual Git hosting. So even if the source code is available and the 3rd party tools aren't broken, work can still be interrupted.

edavis 13y ago

This is true but it misses the point of Github. Nobody denies your blobs are safe and available elsewhere when Github goes down. It's the infrastructure around those blobs that makes Github so popular. It's your issues and pull requests, your wiki, your connection to Travis-CI that are gone when Github goes down. That is why people get angry when it goes down.

nilved 13y ago

What's a "git server?" Set up any machine that can be SSHed into, maybe apt-get install git and you're done. Git is just files.