“We were the scapegoat of the government,” she said. “They (Hamas) warned us three weeks before they taught us a lesson. A huge crowd arrived at the road. They burned fields. They sent incendiary balloons to burn the fields, and the army didn’t take it seriously.”
That seems like an important part of this article. Not to say* what they did wasn't horrific, but seems like something.
My approach was to set it all up internally, create a wireguard VPN accesspoint and only open that up. That way I don't have as much to worry as much within the network (still use generated passwords for things) and able to access it anywhere.
Granted, you asked about opening up to the www. I'd suggest buying a domain through cloudfront, setting up an nginx instance that proxies traffic (think nextcloud.mydomain.com), and have it only accept connections from cloudfront servers.
That allows you SSL termination, pretty good bot coverage, and a nice domain name to share as needed.
Started at college in 08. Multiple Debian internal servers, and now daily driving PopOS since 2018.
No ragrets.