Dota qualifier streams monorepo

This is a monorepository that holds the multiple projects related to list.qualifiers.stream, a site that allows you to see which casters are currently streaming the qualifiers. Click on a folder to get to the projects own READMEs.

The streams on the site are administrated by the same people that run the Dota2Qualifiers twitter. I only created the projects described here to help them and have nothing to do with the actual streams listed on the site.

I never got to open source all previously used projects and instead just rewrote most of the backend as a lot has changed due the new Dota Pro Circuit (2 Major, 1 TI Qualifier per year to now probably more than one qualifer per week). Only the new projects or the ones that still get used will be held in this repository.

This is the now used stack:

• A json data file hosted on Amazon S3 that contains the current streams and maybe some site config. The file contains a special _version key which increases with every version so clients can make sure they are in sync.
• A public AWS IoT topic / stream from which subscribed clients retrieve changes made to the json data file. The update messages are basically JSON Merge patches, just that our version also allows us to partially update arrays. See mergePatch.js in oracle.surge.sh for more information.
• A set of lambda functions available through Amazon API Gateway to update the json data file and publish the changes to AWS IoT.
• A new minimal admin interface that allows you to add and delete streams through the lambda functions above. Updates are retrieved via the AWS IoT stream.
• And finally the main static frotnend hosted on list.qualifiers.stream where everyone can see the current qualifier streams. The site flow is as follows:
  • Wait till the javascript is loaded.
  • Load the json data file containing the streams and display them.
  • At the same time, connect to the AWS IoT stream.
  • Update the streams on the site whenever we receive changes through AWS IoT.
    • If the updated _version key doesn't match our current version, load the json data file again from S3 for a full update.

Before i found out that i can use AWS IoT for this kind of thing i used another project which was providing an Event Source Server that got the streams from a redis pubsub and forwarded them to the connected clients. It was the previous data source for oracle.surge.sh and could be deployed to as many servers as needed for scaling purposes. If someone needs the source for this just send me a mail to the address in my profile. I may publish it as open source one day but it's really just a nodejs http server with some code to handle the redis updates and publish them to the connected clients.