Links mentioned in the tutorial

• Red5
• Eclipse for Java EE Developers
• NetStatusInfo class

About 18 months ago I got my first VPS and figured out how to install RED5, the free open-source alternative to Adobe’s Flash Media Server. It’s a great alternative and the price (0.00 $) is just right. A few weeks ago I decided to upgrade my VPS plan at Vexxhost to a cloud server which meant I had to install everything all over again. Including RED5. I then decided to write a tutorial that includes all the steps needed to get RED5 up and running on your CentOS server.

It takes about 20-40 minutes depending on how much of a brainless copy-paster you are. And on that last note I’d like to add that I take no responsibility if anything goes wrong. These steps are the ones I followed and worked great for me. If for some obscure reason you do something that might mess up your server, I’m not going to take the heat for that.
So, how about it? Let’s get started, shall we?

Requirements

1. SSH access to your VPS
2. The root login to your server
3. Basic knowledge of Java servers, SVN, etc
4. A clue: If you don’t have a clue what you’re about to do here, it means you don’t need to do this and thus don’t need this tutorial.

Let’s go

Prepare your server

JAVA

Red5 is a JAVA server. So you’ll need to have JAVA installed and running on your server. Check if you have JAVA installed by just using the following command:

java

If your server responds with information about the java command, you have java installed. Check to see if you have a valid version of JAVA running by using the following command:

java -version

The first line of the response should be something like “java version “1.6.0_20“. The really important bit here is 1.6.  If that is the case, you can skip this step. If it’s not, you’ll need to update Java. I can’t tell you how to do that. You’ll have to Google that. If you got a response similar to ‘command not found‘, you’ll need to install JAVA.
Installing JAVA on CentOS can be done using Yum. Like this:

yum -y install java-1.6.0-openjdk java-1.6.0-openjdk-devel

Just sit back and watch the lines of text scroll by. This could take a while.
When the scrolling ends: tap yourself on the back. You just installed JAVA on your server. One step closer to success.

RED5 will run on JAVA. We will download the sources later on and then build the RED5 application ourselves. We will build the source using ANT.

ANT

First we need to check if  you have ANT installed. You can check this out by typing:

ant --help

If you get a manual page, you’re in the green. You can skip this step. If you don’t, you’ll have to install ANT. First off let’s change to another directory.

cd /usr/src

We need to download the latest ANT version. You can find the most recent versions here. The one provided in the following step is the most current one at the time of writing. Copy the url and enter it in the following command. This will download the file to your server in the directory /usr/src/.

wget http://opensource.become.com/apache/ant/binaries/apache-ant-1.8.2-bin.tar.gz

This is some kind of strange zip format. We need to uncompress this. (Remember to update the filename in the next step to the one you just downloaded in the previous step)

tar zxvf apache-ant-1.8.2-bin.tar.gz

So now we have all these files in the uncompressed folder, we need to move it to a save place… (Again keep in mind to change the foldername to your version of ANT you just downloaded, 2 steps ago)

mv apache-ant-1.8.2/ /usr/local/ant

So now we have JAVA installed, and ANT is in place. We need to make sure there are some environment variables set. These are global variables with paths to different binaries or applications. ANT and JAVA will need those. Copy and paste the following commands, one by one, BUT MAKE SURE the quotes are valid charachters. I noticed that copy/pasting from websites might mess this up. I suggest you take the time and replace them by hand before actually executing these commands.
export ANT_HOME=/usr/local/ant
export JAVA_HOME=/usr/lib/jvm/java
export PATH=$PATH:/usr/local/ant/bin
export CLASSPATH=.:$JAVA_HOME/lib/classes.zip
echo 'export ANT_HOME=/usr/local/ant' >> /etc/bashrc
echo 'export JAVA_HOME=/usr/lib/jvm/java' >> /etc/bashrc
echo 'export PATH=$PATH:/usr/local/ant/bin' >> /etc/bashrc
echo 'export CLASSPATH=.:$JAVA_HOME/lib/classes.zip' >> /etc/bashrc

All set? Good!
Okay, now ANT and JAVA should know enough about each other to get started. So now we essentially have everything to build the actual RED5 server except for the RED5 source. We will fetch the latest release from the SVN repository at Google Code. For that we will need SVN.

SVN

Let’s see if we have SVN installed:

svn --help

If you get the man pages, you’re free to skip this step. If you don’t: Let’s make it happen!

yum install subversion

If the SVN installation works right away: You’re done here. Skip to the next part. You might get an error like “Error: Missing Dependency: perl(URI) >= 1.17 is needed by package subversion“. That means you’re missing an RPM. Sucks, right? Let’s take care of this…

If your server is a 32bit machine, do the following:

wget ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/releases/7/Everything/i386/os/Fedora/perl-URI-1.35-3.noarch.rpm

If you’re on a 64bit machine:

wget ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/releases/7/Everything/x86_64/os/Fedora/perl-URI-1.35-3.noarch.rpm

Okay, so now you got that new RPM file. You’ll need to add this to the internal list of RPMs (I don’t even know what it’s called). That’ll take care of the error message mentioned above.

rpm -i perl-URI-1.35-3.noarch.rpm

You might get a warning after inserting this command. Don’t worry, I’ve seen it too and yet the world didn’t implode. So ignore that Try installing subversion again using the following command:

yum install subversion

It will ask you if it’s okay to download all this stuff. Of course it is. Type ‘y’ and hit enter to watch the server work away. You should end up with a ‘Complete!‘ message in the end. If you see the ‘Complete!‘ message: It’s okay to feel happy about yourself. You have now subversion running on your server. Or at least a client (from what I got). Getting closer!

Actually installing the RED5 server

Source

It’s finally time to get down to business: RED5. This is why we’re here!
Let’s make sure we’re in the right folder:

cd /usr/src

Let’s get the RED5 source:

svn checkout http://red5.googlecode.com/svn/java/server/trunk/ red5

This will fetch the complete Red5 source and save it in a new folder called, red5 (so in /usr/src/red5)
Now that we have the source, let’s move it to /usr/local/ using

mv red5 /usr/local/

Now let’s dive into the red5 source folder

cd /usr/local/red5

This is the folder where all the source files reside. From here on, we prepare and build the red5 source… This should be interesting. Run these commands one at a time:

ant prepare
ant dist

There’s a (I think the scientific term is) crapload of text going to scroll across the terminal window. Don’t freak out… Just enjoy the show. This is where you call your friends and make them watch the screen as the mass of text freakishly scrolls over your screen. This makes you look very smart. It also makes you look nerdy, but that’s okay. You kind of are… You _ARE_ in fact building a RED5 server… Ohwell… Being a nerd is cool. We can do mighty cool stuff. Let’s wait for the build to complete. After a few minutes you should end up with the last line in your terminal window looking like this:

BUILD SUCCESSFUL

That’s good news! This means that you now have a working RED5 build!
Let’s copy the conf directory from the dist folder to the current directory. (Don’t ask me why… Turns out this is important)

cp -r dist/conf .

Okay, so right now we have a build of the RED5 server. As far as servers go: This one should be ready to rock. Let’s check this out!

./red5.sh

You should get lots of more text scrolling across the screen (again, looks so harcore!). What this does is, it runs the RED5 server. If you wanna make sure your server is actually running, you should be able to see the webroot of Red5 when hitting your server at port 5080 (yourserver.com:5080)(watch the firewall Add ports 5080 and 1935 to the whitelist)
Note that the server is currently only running as long as you keep that terminal window open. Once you close it RED5 stops running. Let’s make sure RED5 can run on its own from now on. Hit CTRL+C to stop the process. (if you visit yourserver.com:5080 again, it should tell you the browser can’t open the page at that address)

Service

We will create a little service script for RED5. Let’s start here:

vi /etc/init.d/red5

You’ll be dropped into vi, a basic UNIX text editor.
Here we will write down the init script that will give us a simple API to start, stop, restart the server and get the status of the server.

Enter the following script into vi. Note: Copy pasting might be buggy, so first copy/paste this script into a local texteditor and make sure all quotes are normal quotes. I ran into this problem. For easy measure: You can download the script here. This version is copy/past-safe

#!/bin/bash
# For RedHat and cousins:
# chkconfig: 2345 85 85
# description: Red5 flash streaming server
# processname: red5
# Created By: Sohail Riaz (sohaileo@gmail.com)

PROG=red5
RED5_HOME=/usr/local/red5
DAEMON=$RED5_HOME/$PROG.sh
PIDFILE=/var/run/$PROG.pid

# Source function library
. /etc/rc.d/init.d/functions

[ -r /etc/sysconfig/red5 ] && . /etc/sysconfig/red5

RETVAL=0

case “$1″ in
start)
echo -n $”Starting $PROG: ”
cd $RED5_HOME
$DAEMON >/dev/null 2>/dev/null &
RETVAL=$?
if [ $RETVAL -eq 0 ]; then
echo $! > $PIDFILE
touch /var/lock/subsys/$PROG
fi
[ $RETVAL -eq 0 ] && success $”$PROG startup” || failure $”$PROG startup”
echo
;;
stop)
echo -n $”Shutting down $PROG: ”
killproc -p $PIDFILE
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/$PROG
;;
restart)
$0 stop
$0 start
;;
status)
status $PROG -p $PIDFILE
RETVAL=$?
;;
*)
echo $”Usage: $0 {start|stop|restart|status}”
RETVAL=1
esac

exit $RETVAL

Once you’ve pasted the text, hit ESC. Then type the following to save and quit vi:

:wq

On the bottom of the screen the ‘:wq‘ should appear (in a status bar style fashion)
Hit enter. Vi should close and the terminal window should look like before. To make sure you saved the init script correctly, just do this once again:

vi /etc/init.d/red5

You should now see the script you pasted earlier. If you don’t, you haven’t saved the script before properly. Go back a few steps and try again. If the script got saved, just enter the following to close vi again:

:q

Since this is unix land, we need to make sure this init script has permissions to actually be executed. Let’s do this! Do it using chmod, like this:

chmod +x /etc/init.d/red5

Now we should be able to start red5 by using this script. Give this a shot

/etc/init.d/red5 start

If your server responds by writing starting Red5: [ OK ], you’re golden. Let’s check the status!

/etc/init.d/red5 status

You should see something like

red5 (pid 11232) is running...

This means that the RED5 server is running on its own. We could close this terminal window and the RED5 server would stay up and running. That’s looking mighty good, right!?
However, whenever we reboot the VPS, the RED5 server won’t start by itself…yet. You know where I’m going with this, right?
In order for RED5 to start when the server boots, we need to do some chkconfig magic. First we need to add the RED5 service to chkconfig:

chkconfig --add red5

Now we need to tell chkconfig that red5 should start asap when booting:

chkconfig red5 on

That should do it… Red5 is installed, you have a simple way of restarting the RED5 service and it starts as soon as possible whenever the server starts. I’d say that’s all we need. Let’s have a little applause for yourself. You did it! You have RED5 running on your server! Now go and have fun with it

Thank you

I think I (= we) should thank a lot of people and communities for what has just been done. All of these apps, binaries, sources and files have been shared for your freedom of using, experimenting and building apps with it. You didn’t have to pay anything for it. You just had to figure out how to use it. A little bit of gratitude is well in order.

At the same time I want to give credit to all of the people who published tutorials and manuals on their own site about how to install RED5 and other apps needed for this to work. Listed below are all the sources I referenced in order to compile this complete guide to RED5-awesomeness.

• http://blog.umbralechoes.com/2010/09/13/how-to-install-red5-0-9-1-on-centos-5/
• http://opensource.become.com/apache/ant/binaries/ 
• http://linuxwindowsmaster.com/how-to-install-subversion-client-on-linux-server/ 
• http://code.google.com/p/red5/source/checkout 
• http://www.sohailriaz.com/how-to-install-red5-server-on-centos-53/ 
• http://www.cs.colostate.edu/helpdocs/vi.html 
• http://linuxcommand.org/man_pages/chkconfig8.html

So I’ve read (millions of times), heard (thousands of times) and seen (I don’t even want to think about it) how people keep using the standard shortcut to take screenshots on a Mac. I can’t really remember how long I did it that way but it sure as hell wasn’t long enough to remember the shortcut. Appearently it’s CMD + SHIFT + 4 for a screenshot (I had to Google this).

What I’ll be showing here is how you can remap this action to one (1) keystroke using standard built-in OSX magic.

1. Open System Preferences
   
2. Go to ‘Keyboard & Mouse’
   
3. Hit the ‘Keyboard Shortcuts’ tab
   
4. Scroll down the the ‘Screen Shots’ group
   
5. I think you’ll be able to handle yourself from here…

I would suggest a screenshot program but apparently the developers in some companies aren’t that bright either…
For example: There’s that TinyGrab thing, which is really making its name ever since Snow Leopard hit the stores and f#cked up GrabUp. They have their own keyboard shortcut and you WOULD think they’d make it easy for you…but they don’t.

I can see how the OSX shortcut is the same as the original ‘short’cut… But what the hell were they thinking for Windows users? Windows users have a ‘Print Screen’ button on their keyboard! What’s wrong with that!? It’s right there! USE IT! (Seriously, it’s stuff like this, that makes me facepalm)(or turn your neighbor into an Oxford-cloth psycho who stalks from office to office with an Armalite AR-10 carbine gas-powered semi-automatic weapon, pumping round after round into colleagues and co-workers)

Anyway: I hope you can remap that insane shortcut to something easier (either for your brain or for your fingers) on your Mac and go on and enjoy your new screenshot-button!

[ Link ]

Onlangs werd op mijn schoolforum gevraagd hoe je nu een mail kunt verzenden vanuit Flash met AS3 (gezien de LoadVars klasse uit AS2 er niet meer is).
Toen besloot ik er een kleine tutorial over te maken, en die is er dan ook gekomen.

Tutorial: Mail verzenden vanuit Flash CS3

Veel plezier.

Vragen en suggesties zijn zeker welkom.

Een van de problemen waar ik al mee gekampt heb is het volgende:
Ik heb een externe USB schijf van 1TB groot. Deze gebruikte ik vroeger altijd op mijn Windows laptop. Het is dan ook maar normaal dat ik op die schijf een NTFS filesystem heb.

Het probleem is dat ik deze schijf nu wil gebruiken op mijn iMac. OSX kan echter alleen lezen vanop NTFS schijven. Vandaar mijn probleem: ik wil kunnen schrijven.
Op het internet heb ik wel oplossingen gevonden, maar geen van deze was echt volledig beschreven. Dat ga ik nu proberen te verbeteren

Eerst en vooral: Voordat je hieraan begint, maak een backup van de cruciale data. Normaal mag er niets mislopen, maar mijn ervaring leert dat Murphy een heel nuchtere persoon was.

1. Ontkoppel de NTFS USB Schijf van je Windows computer. Maak gebruik van ‘USB Apparaat uitwerpen‘! Als je gewoon de USB kabel eruit trekt zal de schijf nog door Windows gelocked zijn, en OSX zal hem niet kunnen mounten.
2. Download en installeer MacFuse.
3. Download en installeer NTFS-3G.
4. Herstart je computer.
5. Als je aangemeld bent, mag je de USB device pas inpluggen.
6. OSX mount de schijf: als je ‘Toon info’ aanklikt bij de schijf zal je bij de rechten zien staan: Read & Write

Ik ben geen Mac-Expert, dus als je vragen hebt kan ik geen antwoord garanderen. Ik sta zeker open voor suggesties, of opmerkingen.

Ik hoop dat ik jullie hiermee iets kon helpen

Om de tut te volgen heb je alleen een text-editor nodig (Notepad is al genoeg. Ik gebruik Dreamweaver ). Een Flashmovie kun je tijdens de tutorial zelf downloaden.

Basis kennis van HTML en ‘weten wat de Canvas in Flash is’ is vereist.

Tutorial:

We willen een Flashobject in een HTML pagina laten weergeven, en de onderliggende HTML gebruiken, om het achtergrond kleur te bepalen van het geheel.

Maak een nieuw html document aan en sla het op als ‘index.htm’ .

We willen nu kunnen bepalen waar we onze Flash willen laten weergeven. Hiervoor maken we een DIV object aan in HTML waar we later onze Flashmovie inladen.

Voeg dit toe aan de BODY in je HTML:

[html4strict]<div id=”flashDIV” style=”width:500px; height:400px; margin-left:-250px; margin-top:-200px;position:absolute;top:50%;left:50%; background-color:#FF0066;”>
Download de Adobe Flash Player om de FlashMovie te zien!
</div>[/html4strict]

In bovenstaande regel zie je meteen ook wat CSS staan. Dat is mijn manier van werken als ik iets wil centreren in het browservenster. Meteen ook een achtergrondkleur ingesteld oor deze DIV. #FF0066 for a better world
Om verder te gaan willen we nu (op een verantwoorde wijze) Flash in deze DIV gaan laden.
Mensen die Microsoft Internet Explorer 6 of Windows Internet Explorer 7 gebruiken zijn ongetwijfeld al op websites gestoten waar men eerst op een Flashobject moest klikken om het te activeren. Dit is een kwestie waar men veel naar verwijst als ‘Het Eolas Patent‘. Het gebeuren rond Microsoft en Eolas had als gevolg dat alle ‘ActiveX objecten‘ in de Microsoft browsers eerst moesten geactiveerd worden. Dit valt op te lossen door SWFObject of andere JavaScript oplossingen te gebruiken. Het fijne hieraan is dat we meteen ook verantwoorde markup in onze broncode hebben.

Download SWFObject.js en zet het in dezelfde map als je index.htm bestand.

Als de HTML pagina geladen wordt moet de browser weten dat we het SWFObject.js bestand willen gaan gebruiken. Dit doen we door de volgende tag in de HEAD-tag van ons HTML document te steken.

De volgende regel moet in de HEAD van je HTML document.

[html4strict]<script type=”text/javascript” src=”swfobject.js”></script>[/html4strict]

Nu hebben we nog een Flashobject nodig dat we in onze DIV willen laden.

Download deze Flashmovie en unzip deze ter hoogte van je index.htm. Je .SWF bestand staat dan in dezelfde map als je index.htm bestand.
Nota: Deze Flashmovie is niet door mij ontworpen of gemaakt. Ik eis geen rechten op.

Nu brengen we onze Flash en de DIV samen, door gebruik van SWFObject.

De volgende code komt onder de DIV in onze HTML.

[html4strict]<script type=”text/javascript”>
var so = new SWFObject(“dodgesquad.swf”, “flashmovie”, “500″, “400″, “8″, “#000000″,”true”);
so.write(“flashDIV”);
</script>[/html4strict]

Als we dit resultaat nu in een browser bekijken zien we een FlashMovie, met 3 actieve mannetjes, maar de achtergrond is nog altijd zwart (het achtergrondkleur ingesteld in Flash). Hiervoor gaan we een extra parameter meegeven aan het SWFObject.

Maak van:

[html4strict]<script type=”text/javascript”>
var so = new SWFObject(“dodgesquad.swf”, “flashmovie”, “500″, “400″, “8″, “#000000″,”true”);
so.write(“flashDIV”);
</script>[/html4strict]

het volgende:

[html4strict]<script type=”text/javascript”>
var so = new SWFObject(“dodgesquad.swf”, “flashmovie”, “500″, “400″, “8″, “#000000″,”true”);
so.addParam(“wmode”,”transparent”);
so.write(“flashDIV”);
</script>[/html4strict]

Als we nu naar het resultaat kijken zien we weer de 3 actieve mannetjes, maar deze keer is de achtergrond pink! Het achtergrond kleur is nu #FF0066, wat we ingesteld hebben in onze DIV.style

Dit is de volledige source code die je nu zou moeten hebben.

[html4strict]<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<meta http-equiv=”Content-Type” content=”text/html; charset=utf-8″ />
<title>Tutorial: Transparante Flash</title>
<script type=”text/javascript” src=”swfobject.js”></script>
</head>

<body>
<div id=”flashDIV” style=”width:500px; height:400px; margin-left:-250px; margin-top:-200px;position:absolute;top:50%;left:50%; background-color:#FF0066;”>
Download de Adobe Flash Player om de FlashMovie te zien!
</div>
<script type=”text/javascript”>
var so = new SWFObject(“dodgesquad.swf”, “flashmovie”, “500″, “400″, “8″, “#000000″,”true”);
so.addParam(“wmode”,”transparent”);
so.write(“flashDIV”);
</script>
</body>
</html>[/html4strict]

Het resultaat kun je hier downloaden of hier bekijken.

Ik hoop hiermee een aantal mensen mee verder te kunnen helpen. Veel succes en vooral veel plezier!