Kaltura CE V4.0 - Pre-installation considerations

This guide is applicable for Kaltura CE version 4.0.0

Please note the following considerations before setting up your Kaltura CE V4.0

Virtual Host Setup

During the installation process, Kaltura sets up the CE to run as a Virtual Host under Apache2. This makes it easier to cleanly support multiple Flash applications and streaming, and lets the various applications run from the virtual root directory regardless of their actual installation paths.
The Kaltura CE uses name-based virtual hosting under Apache2. During installation, the install script will prompt you for the domain name of your machine (or a virtual host, if you have one configured), for example: kaltura.myhost.com. After all installation steps are complete, you will launch the CE with http://kaltura.myhost.com/start.

PHP version compliance

The current version of the Kaltura CE supports both PHP 5.3 and PHP 5.2

Migration from older versions of Kaltura CE

Please note that Kaltura does not provide yet a complete migration path from older versions of Kaltura CE to the current one. If you already run a live web site based on older versions of Kaltura CE, you will need to manually transfer your content and players to work with the new version of Kaltura CE. It’s possible to create a script based on the Kaltura REST API to automate this transfer process using the API’s bulkUpload method.

Pre-distributed setup considerations

The current Kaltura CE installation script is meant for a single server installation. However, when you’re ready to install the Kaltura CE for use in a production environment, you can take the following steps to ease platform distribution when your service scales up.

  • Set up your Kaltura databases on a dedicated server within your environment.
  • Use NFS to set up your storage location on a dedicated file system that can be accessed from your Kaltura server (and later all of the servers you deploy as part of your Kaltura platform setup).
  • Set up your xymon monitoring installation (optional) as the monitoring server, on a dedicated server within your environment
  • For more information about architecture and scaling considerations, please refer to Kaltura CE documentation at http://www.kaltura.org/kaltura-community-edition-kalturace