@Lorne-Kates said in Oh, Discourse …:
You may want to check again.
And again in a few minutes after that.
And hey, maybe, since you'll have to keep checking over and over again, you might as well set up something like Server Cooties to know exactly when it goes down.
Not if. When. And how often.
Nah, experience so far is it takes a lot to kill a Node.js server. I put it through the paces, it is built to handle internal failures when communicating with GitHub and Discourse. When I went to launch, GitHub unexpectantly went down for several hours, which made things a bit interesting.
@Jaloopa said in Oh, Discourse …:
@accalia yeah, but servercooties isn't integrating with Discourse. I predict this service will break roughly every couple of weeks as Discourse randomly changes database schemas, output format and API endpoints.
Yeah, that is probably the best and biggest concern. The Node.js code is pretty solid, but its integration with GitHub and Discourse quickly became overly complex and should those endpoints stop working or cease existence, it won't be easy to resolve.