Discourse's reliance on GitHub can be a liability


(Angus McLeod) #1

Can’t rebuild atm because GitHub is experiencing DDoS.

The launcher fails when trying to pull pups (and/or other dependent repos)

Reducing the exposure to GitHub over time, particularly in build/init scripts, would make sense for similar reasons motivating the s3 deprecation.

A bigger project perhaps, but maybe worth considering, if you’re not already.


(Sam Saffron) #2

I completely agree here, I would like our source of truth repo to be git.discourse.org just need to create the systems to make it happen


#3

A rails project not attached to github? Unimaginable!.

Tongue now out of cheek, I’d say having your own git server may make you less reliable over time - sure github can get dossed, but I’ll bet they have a greater mitigation capacity than a single project such as discourse can bring to bear. Discourse gets hit and youll be down far longer I reckon. So frequency vs severity.

And don’t forget discoverability.


(Sam Saffron) #4

The code would still live in github but we would build from our repo


Bootstrap Failure to connect to GitHub
(Gerhard Schlager) #5

The launcher could use Github as a fallback if Discourse’s own git repository is not available…


(Angus McLeod) #6

This latest round of github.com downtime reminded me of this thread.


(Sam Saffron) #7

I definitely want our source of truth repo to be git.discourse.org, we will get to it this year some time. plugins also add a complication cause we would need a home for them to.


(Erick Guan) #8

The community may help building plugin sites and discourse repo if you ask :smiley: