We're looking to hire a development agency/team with excellent experience with AngularJS, PHP and the AWS Ecosystem.
The goal is to create a customized implementation of the following project Movie Masher: [login to view URL]
You will be working under the guidance of a Movie Masher expert, and as such, you will just need to be extremely comfortable with these core technologies, and the AWS ecosystem as that is where we intend to have this project deployed.
A team/agency is preferred because of the diverse technologies involved, and the fact that we're on a short deadline and need a lot of development hours put in, in a short time-frame.
For detailed information, please refer the below:
Background: The web application that we have developed and currently utilize helps us live stream an event, and after the event is over, the video file is saved to our S3 storage. Your task will be to use Moviemasher to modify the video file for each event, and publish it back to S3.
1. After a live event has been completed, our web application will redirect the user to a new page that will have the MovieMasher interface loaded on it. We will have the S3 directory path and file name of the video file that we need to work with, and will store this path into a variable when this MovieMasher interface page is loaded.
2. You will then have to load that video file in to the Moviemasher interface. We will perform our trimming and other operations on it. After completing all operations, we must be able to export the edited video file back to the S3 storage with a new path name.
3. We should also be able to transcode the final edited video file into multiple bitrates (which should be possible easily using [login to view URL] which has ffmpeg), and save all renditions to the S3 storage.
4. Finally, we intend to run a single main Moviemasher EC2 instance, with an SQS (Simple Queue Service) for job delivery, and access to an S3 bucket for storage. Video conversion jobs will be sent to the SQS, where they will then be executed by the main EC2 instance. We would also like to have a scalable cluster of headless moviemasher instances, that can be started up whenever there is increased demand, and then shut down when the demand has subsided.
Details on this implementation can be found here, as it has already been implemented in an AMI: [login to view URL]
However, we do not want to use the readymade AMI, and would need you to build a new image from scratch.