3 ms·

The last time this happened, it was after they shipped the phone app. I wonder if they have a big feature underway or are just migrating more infrastructure to

by tylfin 6y ago

The last time this happened, it was after they shipped the phone app. I wonder if they have a big feature underway or are just migrating more infrastructure to Azure? EDIT: Either way, some postmortems would be appreciated before more customers have to look for a backup solution...

capableweb 6y ago
If you're working on a serious project, hosting it mainly on GitHub via Git and don't already have a backup solution in place, I'm afraid you're late. But better late than never! Make sure you can always deploy when less reliable services are down, and GitHub has always been one of those. Git makes it incredibly easy as well, as long as you have your CI/CD externalized already.
- tylfin 6y ago
  Yeah, this is very good advice. I think if revenue or product quality is tied to a VCS, having an active-active or active-passive setup is the way to go. Fortunately, I'm on an on-prem product so that investment hasn't seemed worth it yet. This doesn't mean we don't escrow our code, but rather than try to rebuild from source, I just take a short coffee break and wait for the impacted service to come back up :)
dessant 6y ago
I'm still awaiting the promised post-mortem [1] of a retracted blog post [2][3] which has annnounced the deprecation of the GitHub Developer Program. > There must be quite a story behind this - will you be putting up a post-mortem ? (Post mortems of business "outages" are usually more instructional) > Yes. We will. Please stay tuned. [1] https://news.ycombinator.com/item?id=21718171 https://news.ycombinator.com/item?id=21718171 [2] https://news.ycombinator.com/item?id=21718083 https://news.ycombinator.com/item?id=21718083 [3] https://web.archive.org/web/20191205225751/https://developer.github.com/changes/2019-12-05-gdp-deprecation/ https://web.archive.org/web/20191205225751/https://developer...

by tylfin 6y ago

capableweb 6y ago

If you're working on a serious project, hosting it mainly on GitHub via Git and don't already have a backup solution in place, I'm afraid you're late. But better late than never! Make sure you can always deploy when less reliable services are down, and GitHub has always been one of those. Git makes it incredibly easy as well, as long as you have your CI/CD externalized already.

tylfin 6y ago
Yeah, this is very good advice. I think if revenue or product quality is tied to a VCS, having an active-active or active-passive setup is the way to go. Fortunately, I'm on an on-prem product so that investment hasn't seemed worth it yet. This doesn't mean we don't escrow our code, but rather than try to rebuild from source, I just take a short coffee break and wait for the impacted service to come back up :)

dessant 6y ago

I'm still awaiting the promised post-mortem [1] of a retracted blog post [2][3] which has annnounced the deprecation of the GitHub Developer Program. > There must be quite a story behind this - will you be putting up a post-mortem ? (Post mortems of business "outages" are usually more instructional) > Yes. We will. Please stay tuned. [1] https://news.ycombinator.com/item?id=21718171 https://news.ycombinator.com/item?id=21718171 [2] https://news.ycombinator.com/item?id=21718083 https://news.ycombinator.com/item?id=21718083 [3] https://web.archive.org/web/20191205225751/https://developer.github.com/changes/2019-12-05-gdp-deprecation/ https://web.archive.org/web/20191205225751/https://developer...