Getting RED 5 up and running on Ubuntu 9.04
As part of my Rails Rumble team prep, I wanted to document the quickest way to get a Red5 Flash media server up and running on a virtual private server. The Rails Rumble project will actually be using a Linode cloud server, but since I already have a Slicehost account, I did this experimentation on Slicehost.
First fire up a new server on Slicehost (even though it’s not LTS, we’ll use Ubuntu 9.04).
After the server is provisioned, ssh in as root. For simplicity, I’ve done this entire
exercise as root. Obviously on a production server, you’ll want to create the necessary
Next let’s get our server up to date and necessary repos added.
If you are already root, you won’t need the ‘sudo’:
Add this line to the end of your ‘sources.list’ file:
Now run this series of commands from the shell. This will bring Ubuntu
up to date with the latest patches, etc. Also it will install some useful
shell tools like locate to help you quickly find files on the filesystem.
Now install the necessary Java packages and the Ant build tool:
After you have run through the install steps, you can test the success of the
install by checking where java was installed and which version is recognized:
You can do this as a non-root account, but I built Red5 with Ant from the root account.
After the build completes, copy the build output into /usr/share.
Now we can check if Red5 can be brought to life:
We can check with netstat that Red5 is running on the default port of 5080:
And to confirm, connect to port 5080 via telnet:
Go ahead and cancel out of telnet. Confirm that the Red5 start page is accessible via a browser by navigating to:
You should see this Red5 page:
At this point, you can watch the really nice YouTube video that the Red5 team has put together which is embedded on this Red5 start page. It will guide you thru the process of installing a couple of demo applications and then testing them… Remember when you are testing the demo apps to change the ip address of the server you are connecting to. If you are using a remote server, it won’t be ‘localhost’ but the ip address of the remote machine.