Just before I pull the plug, I spinned an EC2 amazon instance and started thinking how I could make that work. I needed a way to have everything ready in minutes. So I went with docker. Docker would help me have the 3 main wordpress components packaged and configured in no time. The DB (just MySQL), the files and the HTTP server. I also needed a way to deploy things fast. Should I go with Ansible? Should I go with Terraform? I didn’t need a configuration management tool, I needed an orchestration tool but at the same time I didn’t want to over complicate things.

I understand that the Internet is full of HOW-to guides on how to dockerize a WP site and how to use docker-compose for that job. There is even an official docker image for wordpress. I needed something simple and modular.

I slowly started preparing a HTTP docker container that would respect my wordpress caching configurations and would also support SSL (Let’s encrypt). So I went with nginx. Nobody ever complained about nginx :). Nginx will serve the supercache generated static files much faster than apache. My wordpress configuration and file structure is pretty plain, so the Nginx docker container would have to be as generic as possible so that anyone can re-use it.

And here is it: https://github.com/alexballas/php-fpm-nginx-wp-super-cache-docker
The repo name is bad, i know..

And a simple example:

$ git clone https://github.com/alexballas/php-fpm-nginx-wp-super-cache-docker.git
$ cd php-fpm-nginx-wp-super-cache-docker
$ sudo docker build -t mynginx .
$ mkdir -p www
$ echo "This is a test HTML file" > www/test.html
$ sudo docker run --name nginx -it -d -p 80:80 -p 443:443 -v `pwd`/www:/var/www/html mynginx
$ curl http://localhost/test.html
This is a test HTML file

So the HTTP part is ready. The only issue I had with it so far, were the incorrect file permissions. This is a known docker issue when using volumes and the host machine UIDs don’t match the container’s UIDs.

https://github.com/alexballas/stream2tv

apt-get -q -y install git $(apt-cache search libevent | grep ^libevent-dev | sort | head -n1 | awk '{print $1}')
git clone http://github.com/darkk/redsocks.git
cd redsocks/
make
echo 'base{log_debug = on; log_info = on; log = "file:/tmp/reddi.log";
daemon = on; redirector = iptables;}
redsocks { local_ip = 127.0.0.1; local_port = 60001; ip = 127.0.0.1;
port = 60002; type = socks5; }' > redsocks.conf
./redsocks -c redsocks.conf
iptables -t nat -N REDSOCKS
iptables -t nat -A REDSOCKS -d 0.0.0.0/8 -j RETURN
iptables -t nat -A REDSOCKS -d 10.0.0.0/8 -j RETURN
iptables -t nat -A REDSOCKS -d 127.0.0.0/8 -j RETURN
iptables -t nat -A REDSOCKS -d 169.254.0.0/16 -j RETURN
iptables -t nat -A REDSOCKS -d 172.16.0.0/12 -j RETURN
iptables -t nat -A REDSOCKS -d 192.168.0.0/16 -j RETURN
iptables -t nat -A REDSOCKS -d 224.0.0.0/4 -j RETURN
iptables -t nat -A REDSOCKS -d 240.0.0.0/4 -j RETURN
iptables -t nat -A REDSOCKS -p tcp -j REDIRECT --to-ports 60001
iptables -t nat -A OUTPUT -p tcp -j REDSOCKS
echo -n "Enter Your Username: ";read myusername;echo -n "Enter Your SSH server hostname/IP: ";read sshhostname; ssh $myusername@$sshhostname -N -D 60002

Example:

$ touch file.txt
$ { pv -bfp file.txt 2>&3 | ssh hdfs@ff1 "hadoop dfs -put - /user/admin/file.txt" 2> /dev/null ;} 3>&1 | tr '\015' '\012'

Step1:
Make sure you have node.js installed on your machine

Step 2:
Install all the extra modules needed for the proxy
user:~$ npm install http-proxy
user:~$ npm install moment

Step 3:
Save the following code to a file (icecast_proxy.js) and change the following values:
ICECAST_HOST
ICECAST_PORT
PROXY_PORT

var httpProxy = require('http-proxy');
var fs = require('fs');
var moment = require('moment');

var count = 0;
var maxcount = 0;
var exists = fs.existsSync("icecast_stats.json");
if (exists) {
    data = fs.readFileSync("icecast_stats.json", 'utf8');
    var datafromfile = JSON.parse(data);
    maxcount = datafromfile.listeners;
} else {
    var filedata = {
        listeners: 0,
        date: moment().format('LLLL')
    }
    fs.writeFileSync("icecast_stats.json", JSON.stringify(filedata));
}
var server = httpProxy.createServer(function (req, res, proxy) {
    proxy.proxyRequest(req, res, {
        host: 'ICECAST_HOST',
        port: ICECAST_PORT,
    });
}).listen(PROXY_PORT);

server.proxy.on('proxyError', function (err, req, res) {
    count = 0;
    res.end();
});

server.proxy.on("start", function () {
    count += 1;
    if (count > maxcount) {
        maxcount = count;
        var filedata = {
            listeners: count,
            date: moment().format('LLLL')
        }
        fs.writeFile("icecast_stats.json", JSON.stringify(filedata), function (err) {
            if (err) {
                console.log(err);
            }
        });
    }
    console.log(count);
});

server.proxy.on("end", function () {
    count -= 1;
    console.log(count);
});

Step 4:
Run the file with node.js
user:~$ node icecast_proxy.js

EXAMPLE
Lets say we have an icecast server, with host: host1.example.com , port 8000 and mount point live.mp3
From here, we have to choose whether we want to run this proxy on the same server, or on a seperate one. If we choose to run it on the same server, he have to define a second port for our proxy to run on, other than 8000. Our proxy’s host will also be host1.example.com. If we choose to run it on a seperate server with with host: host2.example.com, we can still use port 8000 for the proxy. I’ll just go with the first example, where we run it from the same machine.
We set:

ICECAST_HOST -> host1.example.com
ICECAST_PORT -> 8000
PROXY_PORT -> 8001

and run it. Now our listeners can connect to http://host1.example.com:8001/live.mp3
The maximum listeners number is saved to a file called icecast_stats.json which is on the same path with our proxy script.

icecast_stat.json can be accessed with any text editor.