antithetical

Alright, I’ll give you that… Welcome!

Nobody has won, they're just going to the store to get some lube...

Oh certificates are so much fun and you have so many options. From fairly easy to mindboggling complex.

Your current solution is OK if you keep in mind security implications of distributing certs using scripts.

It is not entirely clear where you do your tls-termination but it sounds like that is the Caddy reverse proxy so that is where your certs should be.

Placing them in a location like /etc/ssl/example_com/ as fullchain.pem and privkey.pem is probably easiest. Make sure access rights are appropriate. Then point Caddy at them and it should work. No experience with Caddy itself. If Caddy runs in Docker be sure to map the certificates into the container.

Mind that in this scenario the certificates are only on the Caddy server, connections from the reverse proxy to the services is unencrypted over http. You can't easily use the LE certificates on the services itself without some ugly split-horizon DNS shenanigans.

Alternatively you can set up a PKI with certificates for your services behind the reverse-proxy for internal encryption and do public tls termination in the proxy with Let's Encrypt.

Joplin has their own sync-server you can run as Docker container; free for personal use..

• https://hub.docker.com/r/joplin/server

For my own domains I'm using Migadu since they support unlimited domains per account. Quite happy with them..

Since you frame your question so "elloquently" and you already have many good answers. I'm curious about:

• What is your highest finished education?
• Are you religious?
• What is your primary news source?
• What is your day job?
• Where have you learned how vaccines work?

That's amazing! I've got the same combination on my luggage!

WSL(2) was not Microsoft "being good". It was part of Embrace, Extend, Extinguish.

It was clear Linux won in the server world (not IIS). So why don't you run this lovely Linux as an app in our nice safe OS where we can keep milking you.

I've been using the Index with SteamVR for a few years and so far my experience is pretty good. Running it on an NVidia 1080TI and now 5070TI it works quite smooth. Some minor things aren't supported, like bluetooth (use a script to turn on/off the lighthouses) and the front camera's. But most games I've tried work out of the box in Proton. Performance was also good, even on a 1080TI.

Some games I've played wihtout much issue: Beat Saber, Maestro (they messed up Index controllers, but that is a game issue), Gorn, Alyx, PoewrbeatsVR, Waltz of the Wizard, VRChat, Walkabout Golf, Boneworks and a few more I can't remember right now.

I've been using an Index with NVidia and never encountered this flickering. SteamVR has always worked flawlessly on most games. Except for controller issues but those are more on the game developer (only supporting/testing meta hw) and no support for bluetooth and the front camera's.

Ah too bad, was worth a shot. Other than dissecting the KDE snapshot tool I have no other ideas. Good luck on your search..