Inception

I initially wanted to explore the WordPress Multisite capability because it simply seemed like a neat idea. Lots of sites running on one host.

After some fumbling (I always seem to get involved in some fumbling when I try to do something), I got the WordPress host (named wpm.jmcg.net or wp6.jmcg.net) started in an LXC container on Proxmox (running on a micro Desktop PC) named tiny3.jmcg.net.

There were pretty good instructions for how to set things up on the host.

Not so good were the instructions for how to set up the network environment. I created a wildcard CNAME with my Cloudflare account. I then found I needed to create a new cert to use on my front-end haproxy server, one with a subject name of *.jmcg.net (as I had been using before) and adding a subject alternate name (SAN) of *.wpm.jmcg.net. I use acme.sh to generate LetsEncrypt certs and that has evolved into “normal” certs and certs using “Elliptical Curve Cryptopgraphy”. It seems that acme.sh handles both and adopts -ecc by default, but if the old cert configuration is around, it continues to maintain it. So after I created my new wildcard cert, a renewal of the old-style cert came along an undid it. I think it would be safe to remove the old-style cert folder.

Anyway, now I have three “sites” set up in this network, named “site1”, “inception”, and “involution”. The names don’t mean much, they were just something to call the sites.

I have kept the Twenty Twenty-Five theme that came by default with the WordPress install. I have not yet added any categories, tags, plugins, or media. So this site remains very bare-bones.

I’m not sure I have enough original content to fill up *one* blog, much less 3 or 6 or whatever my count of sites is up to.

There’s also some background bookkeeper tasks such as privacy policy, an “about” page, etc. I’ll get to them as I find time.