Internal server (Home Assistant etc.): domus
External server (Nextcloud etc.): nimbus
Router/firewall: murus

I believe so—see Wake-on-LAN.

deleted by creator

One under-appreciated aspect of Docker is that it forces you to document all your setup steps in your dockerfile and docker-config files.

I haven’t tried it because I’ve read a lot of negative discussions of it—and because (by my understanding) the only reasonable use case would be if there were a large number of users and each user is likely to have copies of the same files but don’t want to expose their files to each other (so you can’t just manually de-dupe).

Does a Chinese chef get extremely angry at an Italian chef for making pasta?

the tech community keeps waiting for everyday people to take the baton of self-hosting. They never will—because the effort and cost of maintaining self-hosted services far exceeds the skill and interest of the audience.

The same argument could have been used a century ago to claim that everyday people would never switch from trains to private cars, because the effort and cost of maintaining a car exceeds the skill and interest of most travelers. That may have been true at one point, and may be true again in the future—but it’s contingent on changing circumstances, not a categorical truth.

Another advantage of Nextcloud over Syncthing is selective syncing: Syncthing replicates the entire collection of synced files on each peer, but Nextcloud lets clients sync and unsync subfolders as needed while keeping all the files on the server. That could be useful for OP if they have a terabyte of files to sync but don’t have that much drive space to spare on every client.

A typical use case is to forward a single port to the proxy, then set the proxy to map different subdomains to different machines/ports on your internal network. Anything not explicitly mapped by the reverse proxy isn’t visible externally.

Also Doctorow’s novella “Unauthorized Bread”.

At least Oracle Weblogic is being useful for someone.