HuPI

From Wildsong
Revision as of 18:09, 1 January 2017 by Brian Wilson (talk | contribs)
Jump to navigationJump to search

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.

2017-Jan-01

Currently everything is running in a virtual machine. 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.

Services required

  • Web service
  • Email
  • Mailman

Web service

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

Email

Using postfix

Mailman

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.

Docker set up

I see this running in two docker containers, one for nginx and one for mailman/postfix.

Persistent file storage would be a volume on the host. I can't see any need for any databases at akk.

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.

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