[Bug 414188] [NEW] implement direct-to-S3 uploads on the transmit-based upload page
Fabricio Campos Zuardi
This bug is the followup for Bug #410914.
We decided that we are doing the upload direct to s3 thing, even if not
for all users, at least for Ace's matterial, in order to save some time
and not have to upload things twice (2k clips and counting).
So, this bug covers the necessary tasks to get our current upload clip
page that uses the swf based jquery transmit uploader, adapted to:
1- upload the files to an amazon S3 bucket, as described on http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1434
2- create a shell script to create auxiliary files that will contain the s3 keys to be used for each file
3- use those correct s3 key for the new file that will be saved on s3 based on the data that the shell script created
(maybe) 4- add extra fields for manually entry more information about the files being sent — this should probably be covered by a new bug yet to be created, so don't worry about that for now.
** Affects: publicvideos
Importance: Medium
Assignee: jgalvez (jonas-codeazur)
Status: New
** Tags: contributor s3 transmit upload
** Changed in: publicvideos
Importance: Undecided => Medium
** Changed in: publicvideos
Milestone: None => august-15-weekend
** Changed in: publicvideos
Assignee: (unassigned) => jgalvez (jonas-codeazur)
--
implement direct-to-S3 uploads on the transmit-based upload page
https://bugs.launchpad.net/bugs/414188
You received this bug notification because you are a member of
Publicvideos Dev Team, which is the registrant for Public Videos.
Status in Public Videos: New
Bug description:
This bug is the followup for Bug #410914.
We decided that we are doing the upload direct to s3 thing, even if not for all users, at least for Ace's matterial, in order to save some time and not have to upload things twice (2k clips and counting).
So, this bug covers the necessary tasks to get our current upload clip page that uses the swf based jquery transmit uploader, adapted to:
1- upload the files to an amazon S3 bucket, as described on http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1434
2- create a shell script to create auxiliary files that will contain the s3 keys to be used for each file
3- use those correct s3 key for the new file that will be saved on s3 based on the data that the shell script created
(maybe) 4- add extra fields for manually entry more information about the files being sent — this should probably be covered by a new bug yet to be created, so don't worry about that for now.
Fabricio Campos Zuardi
the files for us…
we will use this following docs to learn how to do it:
http://permadi.com/blog/?p=965
http://code.google.com/p/as3crypto/
Fabricio Campos Zuardi
* Jonas have made a sample simple upload view on http://github.com/fczuardi/publicvideos/commit/3fa1c1c7726f8413505d79efb07780846d7dbe48
* after that we thought it would be cool if the contributor didn't had to enter the s3 key manually, which in our case is a file hash digest (sha1, but we might change to md5, not set in stone)
* in order to make this hash calc browser based we would have to replace our current uploader.swf with a new one customized for our needs
And that's basically what is delaying the close of this one. I was
responsible for coding this replacement swf and it turns out I had to do
some intense investigation.
The good news is that we now have our first official publicvideos
article at http://wiki.publicvideos.org/dev/articles/browser-
based_file_hash_generator
The bad news is that we may need to push this direct-to-s3 upload plan
for after the alpha, and upload the clips we have using the existing
daemon, which works for now.
I am re-targeting this bug.
** Changed in: publicvideos
Milestone: august-15-weekend => beta-launch
** Changed in: publicvideos
Assignee: jgalvez (jonas-codeazur) => Fabricio Campos Zuardi (fabricio)