6 Commits (f8d10dacdf23c7b2653e8122c5d92839e30e41ff)

Author	SHA1	Message	Date
Mike Lang	5b2a1ef6b7	cutter: Implement actual cut methods ... Each method is fairly complicated, but is self-contained and can be examined independently. cut_jobs in particular contains several extra helpers and directs control flow via some iterators. This is unfortunately nessecary due to the requests interface.	6 years ago
Mike Lang	ae809c696c	cutter: Outline of how main cutter run loop works ... This commit only lays out the main loop, showing the high-level flow and defining shared utilities. This is for clarity. The actual methods that do the work will be implemented seperately.	6 years ago
Mike Lang	80c1a66aa0	cutter: Implement TranscodeChecker ... It runs on an interval, fetching all videos in TRANSCODING from the DB, checking them against youtube, and then updating any that are done. It should be noted that youtube somewhat lies about what being "done" means, but this is a better approximation than nothing.	6 years ago
Mike Lang	3ce8360a1e	cutter: Add database manager and connections ... One connection each for transcode checker and cutter. We don't need more than one each since both workers only ever do one thing at once.	6 years ago
Mike Lang	fdd245a6d9	cutter: Add lightweight youtube client ... Provides basic youtube api calls, and gets passed into both transcode checker and cutter. The official youtube client library is many orders of magnitude larger and more complicated, and can't actually do what we want (stream an upload of unknown size).	6 years ago
Mike Lang	e4b6110fd7	cutter: Add initial outline ... The cutter has two jobs: * To cut videos, taking them through states EDITED -> TRANSCODING * To monitor TRANSCODING videos for when they're complete We run these as separate greenlets with their own DB connections, and if either dies we gracefully shut down the other.	6 years ago