Closed codersquid closed 10 years ago
This will likely turn into a freshly shaved yack....
These 4 uploaders have a similar structure: archive_uploader.py blip_uploader.py vimeo_uploader.py youtube_uploader.py They do not rely on veyepar they can be run standalone (mainly for testing) they all define Uploader.upload() but they are all a little different.
They all have a corresponding post_foo.py that is the veyepar process which uses foo_uploader
it is klunky to mix and match what services veyepar uses, but that doesn't change much either.
it is time to make an abstract class? (I don't think so.. but maybe and it will be fun to talk about)
The most recent one: https://github.com/CarlFK/veyepar/blob/master/dj/scripts/archive_uploader.py
It also has helper functions, like make_bucket()
I think it would be fun to set up a multi-headed queue where each uploader handles videos in the queues. they will log problems and you can rerun uploading jobs on the problems after you look through to see if the problems were just timeouts and trivial things versus things that need attention.
I like interfaces, so whatever that means in python terms (making an abstract class with exceptions if something isn't implemented, but is called) or whatever, do that.
but for now, if you want this to happen today, slay the yak and have a bbq.
We can host python videos with pyvideo's rackspace service.
You can see an example script for uploading files here,
https://github.com/codersquid/pmc/commit/5c47b886119a455fbd07901e6b41d4cec0d40d7a
Will has some improvements for uploading folders that he has on top of what I've got and when he checks that in I can show you.
we'll need to generate an api for veyepar.