| 1 | 0. Setup indytube.conf - see README and INSTALL |
|---|
| 2 | Its helpful to know where the log files are being written so you can watch them , as you run and configure indytube |
|---|
| 3 | |
|---|
| 4 | 1. Setup the configuration file indytube.conf so that it searches Plone's external storage file path |
|---|
| 5 | This is controlled by VIDEO_FILE_DIRECTORY. It will walk recursively down this directory, and pick up |
|---|
| 6 | every eligble file. Eligble in this case means any file ending with an extension define |
|---|
| 7 | in CONVERT_THESE in the [encoder] |
|---|
| 8 | eg |
|---|
| 9 | [paths] |
|---|
| 10 | VIDEO_FILE_DIRECTORY=/opt/instances/zope-testing/var/files/Members |
|---|
| 11 | FLV_FILE_DIRECTORY=/var/www/flv-files/ |
|---|
| 12 | |
|---|
| 13 | # The next section is where you set indytube to find the Cheetah template (the meta-HTML) |
|---|
| 14 | and where to output the files , and what extension they will have. |
|---|
| 15 | |
|---|
| 16 | INCLUDE_FILE_DIRECTORY=/opt/instances/zope-testing/var/files/Members |
|---|
| 17 | INCLUDE_FILE_SUFFIX=.flv.inc |
|---|
| 18 | INCLUDE_TEMPLATE=/opt/indytube/plumi.template |
|---|
| 19 | |
|---|
| 20 | all transcoded video go into a web-accessible area, eg FLV_FILE_DIRECTORY |
|---|
| 21 | |
|---|
| 22 | 2. Setup apache2 to serve these .flv files, from FLV_FILE_DIRECTORY |
|---|
| 23 | |
|---|
| 24 | Possible virtual host stanza for apache2 |
|---|
| 25 | NameVirtualHost 66.135.41.120:80 |
|---|
| 26 | <VirtualHost 66.135.41.120:80> |
|---|
| 27 | ServerName flv.engagemedia.org |
|---|
| 28 | ServerAdmin webdev@engagemedia.org |
|---|
| 29 | DocumentRoot /var/www/flv-files |
|---|
| 30 | DirectoryIndex index.html index.htm index.shtml index.cgi index.php |
|---|
| 31 | ErrorLog /var/log/apache2/flv-files-error.log |
|---|
| 32 | LogLevel warn |
|---|
| 33 | CustomLog /var/log/apache2/flv-files-access.log combined |
|---|
| 34 | </VirtualHost> |
|---|
| 35 | |
|---|
| 36 | 3. Make sure the template is referencing the correct URL paths to get the files, flowplayer, cortado applet etc |
|---|
| 37 | Again, this is controlled by the indytube.conf file |
|---|
| 38 | |
|---|
| 39 | eg |
|---|
| 40 | [urls] |
|---|
| 41 | FLOWPLAYER_LOCATION=http://testing.engagemedia.org/flowplayer/FlowPlayer.swf |
|---|
| 42 | VIDEO_SERVER_URL=http://flv.engagemedia.org/ |
|---|
| 43 | SPLASH_IMAGE_BASE=http://testing.engagemedia.org/flowplayer/ |
|---|
| 44 | SPLASH_IMAGE_FILE=Play_v2_trans.png |
|---|
| 45 | |
|---|
| 46 | So, you need to copy FlowPlayer.swf (or whatever filename you use) to FLOWPLAYER_LOCATION |
|---|
| 47 | note , you can use different virtual host names if you like. So you can serve the flowplayer swf from |
|---|
| 48 | one app server, and use another as the reference for downloading/streaming videos (VIDEO_SERVER_URL) |
|---|
| 49 | (or not. you can just use apache2 for both) |
|---|
| 50 | |
|---|
| 51 | The is image referenced in SPLASH_IMAGE_FILE should be copied to the virtual host referenced by VIDEO_SERVER_URL |
|---|
| 52 | |
|---|
| 53 | Note: SPLASH_IMAGE_FILE is actually loaded from the web relative to VIDEO_SERVER_URL , not SPLASH_IMAGE_BASE |
|---|
| 54 | This needs correcting in the source, flowplayer changed since the confg var names was initially choosen |
|---|
| 55 | |
|---|
| 56 | |
|---|
| 57 | 4. Fullscreen mode in flowplayer. |
|---|
| 58 | Install fullscreen.js/html and swfobject.js into the VIDEO_SERVER_URL virtual host |
|---|
| 59 | Configure fullscreen.js to use the correct virtual host url to open fullscreen.html |
|---|
| 60 | Configure fullscreen.html to be the html you want to display when the user watches the movie in "fullscreen" mode |
|---|
| 61 | |
|---|
| 62 | eg to do steps 3 and 4 you might |
|---|
| 63 | $ sudo cp fullscreen.js fullscreen.html swfobject.js ~/src/flowplayer/FlowPlayer.swf /var/www/flv-files/ |
|---|
| 64 | |
|---|
| 65 | -- |
|---|
| 66 | andy@engagemedia.org |
|---|
