861a426395
Bytes returned from the database are a "memoryview" and not a bytes object. These mostly behave the same, but one difference is that Flask recognizes a bytes object as something it can send as-is, whereas a memoryview ends up using its generic "iterable" processing. This results in sending every individual byte of the result as a single part of a HTTP chunked encoding response, adding 5 bytes and a syscall to every byte returned. The solution is to explicitly convert it to bytes before returning. |
3 weeks ago | |
---|---|---|
.github/workflows | 4 weeks ago | |
api_ping | 1 year ago | |
backfiller | 1 year ago | |
bus_analyzer | 1 year ago | |
buscribe | 1 month ago | |
buscribe-web | 1 month ago | |
buscribe_api | 3 weeks ago | |
chat_archiver | 2 months ago | |
common | 3 weeks ago | |
cutter | 4 weeks ago | |
db_scripts | 5 years ago | |
downloader | 1 year ago | |
graphs | 1 year ago | |
monitoring | 1 year ago | |
nginx | 1 month ago | |
playlist_manager | 3 months ago | |
postgres | 3 weeks ago | |
restreamer | 1 month ago | |
segment_coverage | 1 year ago | |
sheetsync | 3 weeks ago | |
thrimbletrimmer | 3 weeks ago | |
thrimshim | 3 weeks ago | |
zulip_bots | 3 weeks ago | |
.gitignore | 1 year ago | |
.gitmodules | 2 years ago | |
.prettierrc.yaml | 3 years ago | |
.travis.yml | 5 years ago | |
DATABASE.md | 3 months ago | |
INSTALL.md | 1 year ago | |
LICENSE | 5 years ago | |
README.md | 1 year ago | |
SecurityModel.md | 5 years ago | |
build | 4 weeks ago | |
docker-compose.jsonnet | 3 weeks ago | |
generate-docker-compose | 5 years ago | |
generate-flamegraph | 6 years ago | |
get-build-tag | 5 years ago | |
initial-design-doc.pdf | 6 years ago | |
k8s.jsonnet | 1 year ago | |
playlist-audit | 4 weeks ago |
README.md
Wubloader is a system for saving, re-serving and cutting into videos of a target twitch (or probably other HLS, but some twitch specifics are assumed) stream.
It was designed to serve the needs of the Video Strike Team as part of Desert Bus For Hope.
A full design doc can be read at initial-design-doc.pdf, but a brief overview of the components:
downloader
grabs segments from twitch and saves them to diskrestreamer
serves segments from disk as well as playlist files allowing them to be streamedbackfiller
queries restreamers of other servers in order to pick up segments this server doesn't have already, ie. it replicates missing segments.cutter
interacts with a database to perform cutting jobssheetsync
syncs specifc database columns to a google doc which is the primary operator interface.thrimshim
acts as an interface between thethrimbletrimmer
editor and the database.thrimbletrimmer
is a browser based video editor.segment_coverage
regularly checks whether there is complete segment coverage for each hour.playlist_manager
adds videos to youtube playlists depending on tags.chat_archiver
records twitch chat messages and merges them with records from other nodes.database
hosts a Postgres database to store events to be edited.nginx
provides a webserver through which the other components are exposed to the outside world.common
provides code shared between the other components.monitoring
provides dashboards to allow the wubloader to be monitored.
Usage
All components are built as docker images.
Components which access the disk expect a shared directory mounted at /mnt
.
A docker-compose file is provided to run all components. See docker-compose.jsonnet
to set configuration options, then generate the compose file with ./generate-docker-compose
.
Then run docker-compose up
.
There is also a kubernetes-based option, but it is less configurable and only fully supports replication and editing nodes. Basic support for running the database and playlist_manager has been added, but not tested. See k8s.jsonnet for details.
Further details of installing and configuring the backfiller are provided in INSTALL.md.