HuPI

2017-Jan-01

Currently everything is running in a virtual machine called Hub. This was the way to go a few years ago, now I have just the one VM running there so it's just as much work as running a separate server.

I am considering what it would take to use Docker containers instead. The big advantage for me would be that Dockers are very portable, I can copy them and run them anywhere. The only thing tying me to one machine is the mapping between DNS and a fixed IP address. (Which is true with the virtual machine.)

I chose to try QEMU/KVM to support the virtual machines on Dart and I want to get rid of that, it's the only place I ended up using it. I want to use VirtualBox when I need VM's, it's better. So even if I don't use Docker I want to get rid of QEMU.

2015-Jan-25

Moved IHPVA.org to Tektonic.net to support mailing list volume and dragged HuPI over at the same time.

Moved back to my own server at CDS to save money.

Dockerization =

Services required

• Web service
• Email
• Mailman

Web service

Strictly plain vanilla HTTP server. Needs CGI support for Mailman.

Starting with Dockerizing the simple hupi wen site, then decide what direction to go with mailman... should probably be a separate docker

Theo would be able to access the storage area by connecting to Dart, and he already has credentials to do that. It should look no different.

Currently it's running on nginx as a virtual host. The router Aurora points incoming traffic at the IP 192.168.89.239. It does this on a port by port basis.

cat hupi.org
server {
        listen 192.168.89.239:80 default_server;
        server_name hupi.org;

        root /var/www/hupi.org/html;
        index index.htm index.html;

        location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
             try_files $uri $uri/ =404;
        }
}

Email

Using postfix as the MTA.

Mailing lists http://hupi.org/cgi-bin/mailman/listinfo

The only list left is "vph", I shut all the others down over a year ago.

It should still be possible to connect to the postfix/mailman container via exec to run mailman commands, in fact you could run the commands directly (no shell.) I should be able to make aliases for that.

Mailman

docker pull macropin/mailman:latest

docker run --rm -ti --name mailman \
 -p 80:80 -p 25:25 \
 -e MAILMAN_URLHOST=www.example.com \
 -e MAILMAN_EMAILHOST=example.com \
 -e [email protected] \
 -e MAILMAN_ADMINPASS=foo \
 docker.io/macropin/mailman