|
Revision 196, 1.3 kB
(checked in by andy, 17 months ago)
|
|
update for red5
|
| Line | |
|---|
| 1 | The basic idea |
|---|
| 2 | ------------- |
|---|
| 3 | |
|---|
| 4 | Indytube tries to encode media files into flv and ogg theora codec files. |
|---|
| 5 | If successful, a snippet of html is produced, when included inside a typical CMS templating system, will include a browser widget for the appropriate media player (a FLV plugin or OGG plugin) |
|---|
| 6 | |
|---|
| 7 | So, you need to configure indytube to see your incoming video files directory, and where to put encoded media. |
|---|
| 8 | You will also need to configure the virtual hosts that serve you media. |
|---|
| 9 | For this you will need a streaming (icecast2, red5) or a web server will do (apache2) |
|---|
| 10 | |
|---|
| 11 | see README for more details about configuring indytube.conf and include.template, and the required third party software |
|---|
| 12 | |
|---|
| 13 | Read INSTALL.plone for a plone / apache2 setup |
|---|
| 14 | Read INSTALL.red5 for a very basic configuration for red5 streaming server. |
|---|
| 15 | |
|---|
| 16 | Running indytube |
|---|
| 17 | ---------------- |
|---|
| 18 | Remember to have your permissions set correctly for the user you will start indytube as for the directories inside the Plone instance. |
|---|
| 19 | |
|---|
| 20 | You can debug problems by watching the log files generated, check the [urls] section of the indytube.conf |
|---|
| 21 | |
|---|
| 22 | |
|---|
| 23 | invoke as |
|---|
| 24 | $python indytube.py |
|---|
| 25 | to see cmd line messages |
|---|
| 26 | |
|---|
| 27 | or to run as a background process |
|---|
| 28 | $./run_indytube.sh |
|---|
| 29 | |
|---|
| 30 | watch for the logs and lock files , in the directories configured in indytube.conf |
|---|
| 31 | You may have stale lock file left around from indytube crashes. |
|---|
