= Quick install =

== Installing MediaMosa in 1 minute ==

Download: http://mediamosa.org [[BR]]
You need: LAMP, FFMpeg, Lua (LPEG)[[BR]]
Recommended: Lav2yuv (MJPEG Tools) ...

Installation: Drupal / MediaMosa install profile

== How can you install MediaMosa? ==

The main goal for this section of the wiki is to guide you through the first steps with MediaMosa. It explains the basics of installation.

PS. MediaMosa doesn't provide video transcoding tools (eg. video to flash coder).

 * [wiki:"Pre requirement"]
 * [wiki:"Get MediaMosa"]
 * [wiki:"Installing MediaMosa"]
 * [wiki:"Configuring MediaMosa"]
 * [wiki:"Tuning MediaMosa"]
 * [wiki:"FAQ"]

== Installing MediaMosa Front-End ==

=== Introduction ===

MediaMosa can be split up into 2 parts;

 1. Front-end website.
 2. Back-end software.

The front end website is something like youtube (its what the user will see), The back-end software is MediaMosa.

So in order to use MediaMosa you must have both. MediaMosa its self as we provide it, is only back-end software. We do provide front-end software to get you started, both for Drupal 6 and Drupal 7.

The communication between front-end and back-end is handled by REST. These REST interfaces allows the front-end to query MediaMosa. This is build like this to make it scalable. Some websites will need a lot of power, so more REST interfaces can be setup, so load can be divided.

The other part is the front-end. We have multiple solutions to get you started;

=== WLE ===

WLE (is outdated, but can be easy start) (drupal 6);
 http://mediamosa.org/content/mediamosa

Although we do not recommend you using WLE, but its stable and easy to use. It will allow you to test MediaMosa as it can upload and play media.

=== CK ===

The 'CK' (construction kit) will allow you to build front-end websites. We got drupal 6 and drupal 7 versions, where the drupal 6 version is the most stable atm.
 http://mediamosa.org/content/mediamosa-ck

All front-ends need extra software. In case of WLE you need the VPX-connector module.

The CK however need the SDK;
 http://mediamosa.org/content/mediamosa-sdk

The connector module in the SDK provides the software to communicate between MediaMosa and your website CK.

The Drupal 6 version will stay as it is and will not be developed further (beside bug fixes).

The Drupal 7 CK has more options and is more integrated into Drupal. It uses the Media module for Drupal 7, which is developed by Drupal.

In the CK Drupal 7 version, we also provide a profile (mediamosa_profile). To quickly setup a front-end with CK Drupal 7;

 1. Download Drupal 7 from drupal.org.
 2. Untar/unzip Drupal 7.
 3. Take MediaMosa CK and MediaMosa SDK and copy all directory (except mediamosa_profiles) to the sites/all/modules directory of your front-end installation.
 4. Copy the mediamosa_ck_profile to /profiles directory of your front-end installation.
 5. Goto /install.php on your front-end and select the MediaMosa CK profile and start the installation.
 6. If everything goes well you got a running MediaMosa front-end installation.

All front-ends need a client application on the back-end. A client-application is a container where media is stored. This container is used per website. So if you more than one website, you create multiple client applications. So 1 website might store movies, the other music. etc. This way you can reuse the back-end on multiple websites. Also client applications can share their media between them, so uploads on website A can be made visible on website B.

You need to create a client application on the back-end admin of mediamosa. You need to provide a name and password. That name and password is what you need to enter into the MediaMosa connector (or VPX-connector on WLE). It also need the default application REST interface, by default its app1.mediamosa.local. When saving the form at the connector, it will check if the client application is working and communication between front-end and back-end is working.

If connector is setup and is able to connect, then you can start uploading and playing media. (although you might need to tweak some settings in MediaMosa back-end admin).