HuPI: Difference between revisions

From Wildsong
Jump to navigationJump to search
← Older edit
VisualWikitext
Brian Wilson (talk | contribs)
Bureaucrats, restrict, Administrators, uploaders
11,533 edits
Brian Wilson (talk | contribs)
Bureaucrats, restrict, Administrators, uploaders
11,533 edits
m Pulled changes from the old site
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
2017-Jan-01
2022-November-11


Currently everything is running in a virtual machine called [[Hub]].
We're moving from shared hosting at Bluehost.com back to a VPS at Tektonic.net because it's now cheaper.
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,
== Web service ==
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
For HuPI it is in /home/hupi. The web pages are all in /home/hupi/content/.


Moved IHPVA.org to Tektonic.net to support mailing list volume
It's running in a Docker container called "hupi", using the Caddy webserver.
and dragged HuPI over at the same time.


Moved back to my own server at CDS to save money.
There is another Docker container called "caddy-proxy" that handles the certificates for the HTTPS encryption. It's also running Caddy and it functions as a reverse proxy.


== Dockerization ===


Services required
== Email ==


* Web service
These are old notes, it's not set up yet.
* 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.
 
=== Email ===


Using postfix as the MTA.
Using postfix as the MTA.
Line 54: Line 28:
=== Mailman ===
=== Mailman ===


  docker pull macropin/mailman:latest
  docker pull macropin/mailman
 
I can direct traffic from the router to any particular port
so I can run SMTP on port 2525 and send port 25 traffic to it.


  docker run --rm -ti --name mailman \
  docker run --rm -ti --name mailman \
   -p 80:80 -p 25:25 \
   -p 2525:25 -p 8025:80 \
   -e MAILMAN_URLHOST=www.example.com \
   -e MAILMAN_URLHOST=list.hupi.org \
   -e MAILMAN_EMAILHOST=example.com \
   -e MAILMAN_EMAILHOST=hupi.org \
   -e MAILMAN_ADMINMAIL=admin@example.com \
   -e MAILMAN_ADMINMAIL=admin@hupi.org \
   -e MAILMAN_ADMINPASS=foo \
   -e MAILMAN_ADMINPASS=yersecretpassword \
   docker.io/macropin/mailman
   macropin/mailman
 
You should be able to connect to the 2 services, HTTP and SMTP.
 
telnet localhost 8025
telnet localhost 2525

Latest revision as of 01:30, 14 November 2022

2022-November-11

We're moving from shared hosting at Bluehost.com back to a VPS at Tektonic.net because it's now cheaper.


Web service

For HuPI it is in /home/hupi. The web pages are all in /home/hupi/content/.

It's running in a Docker container called "hupi", using the Caddy webserver.

There is another Docker container called "caddy-proxy" that handles the certificates for the HTTPS encryption. It's also running Caddy and it functions as a reverse proxy.


Email

These are old notes, it's not set up yet.

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

I can direct traffic from the router to any particular port so I can run SMTP on port 2525 and send port 25 traffic to it. 

docker run --rm -ti --name mailman \
 -p 2525:25 -p 8025:80 \
 -e MAILMAN_URLHOST=list.hupi.org \
 -e MAILMAN_EMAILHOST=hupi.org \
 -e [email protected] \
 -e MAILMAN_ADMINPASS=yersecretpassword \
 macropin/mailman

You should be able to connect to the 2 services, HTTP and SMTP. 

telnet localhost 8025
telnet localhost 2525
Retrieved from "https://wiki.wildsong.biz//index.php?title=HuPI&oldid=13573"