141–150 of 197 posts
Earlier quoted context omitted.
Sounds like an argument against micro services?
Only if you don't stop to consider the alternative.
Everyone is saying: just work on your local repo. But GitHub is way more than just git. There's bug tracking, code review, continuous integration, etc etc. Making your organisation too dependent on a remote service can indeed be a scary prospect and I'm not sure what GitHub offers to mitigate this.
Not that I'd suggest using it for every scenario, but being aware of alternatives is always a good thing.
[0] http://fossil-scm.org/index.html/doc/trunk/www/index.wiki
What 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...
They could also have a base version of the site that's read-only for source or binaries to allow customers access to the data to fall back to whenever problems happen in more complex functions. Keep it running in some form while they fix things. They might also similarly sell Git appliances w/ high-availability that themselves plug into multiple colo's or cloud providers mirroring changes in the repo to the Github site. Just a wild idea as I have no idea if that's marketable.
What 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...
At this point Github is a national security risk. The amount of passwords, keys, hashes, code, data uploaded to that system is massive. I am sure that government agencies, contractors, multinational defense departments, etc are dumping things on there hourly. Will it get hacked ? Get your popcorn out. It will happen.
Earlier quoted context omitted.
The argument is with a self-hosted solution you can choose your "danger times". If you know you have a major deliverable coming up, you can choose not to touch your git server until it's at a somewhat safe moment to do so.
While it definitely sounds like a good idea, every single time I've seen it applied, the reason was the opposite. It was essentially "we've got so little control over our stuff that we'd rather not touch". Mostly goes along with lack of backups, lack of change management, and lack of automated rebuild procedure. If you have "danger times", then any unplanned disruption in that time will hurt so much more.
What 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...
What 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...
Earlier quoted context omitted.
How is the GitHub marketplace a runtime dependency? Code review, project management, build bots or whatever else should NOT affect the availability of your website.
Sure, if you measure uptime of your business and dev team by whether you're serving pages. I wouldn't. If Github being down means you're not fixing your site today, I'd call it a runtime dependency.
Deploying/scaling is somewhere in the middle.