|
The Movie Masher distribution includes several example deployments, some of which are simpler to install than others. At bare minimum, users need an up-to-date browser with Adobe Flashâ„¢ Player installed and the server must be able to deliver SWF files.
Learn more in Requirements.
All the example deployments come preinstalled on
the Server AMI - a prebuilt LAMP-based web server available for launch and customization within Amazon's EC2 global cloud infrastructure. There is no additional cost for running the server beyond Amazon's low hourly rate - they charge no setup or ongoing fees.
Learn more in Server.
Typically folks want to run the most complex 'transcode' example, with its support for preprocessing of uploads and rendering of mashes back into true video format. This requires at least one running instance of
the Transcoder AMI
- a different server also in EC2 which provides an API into these functions.
Learn more in Transcoder.
The 'transcode' example can be configured to access Transcoder instances either through REST or SQS, and store the resultant file either locally or in S3. It's best to decide upfront if either SQS or S3 will be used, since this affects how the machine should be launched.
Learn more in Architectures.
Additional documentation, including step by step instruction, is available from the various README* files in the distribution within each example's directory.
|