

I have a Google container and a Facebook container to somewhat segment those accounts from everything else (obviously they’re both sophisticated enough that it doesn’t limit tracking much. But it’s something).
It does make Google login a bit awkward if I try to log in from a nom-google container though unfortunately. I usually have to reopen in the Google one.
And I have one for my work accounts when I need to check work email from my personal PC. I don’t want to accidentally log in to that account casually.
If you’re hosting static content it’s a lot easier. If you’ve only opened ports 80/443 and don’t have any kind of user input or scripting you’re (probably) fine. Most likely you’d get DOS’d before someone would hack you. Assuming you’re keeping your software up to date.
In general though limit what is exposed to the Internet. In this case don’t open any extra ports.
If you want to be more secure (likely overkill for most threat models), treat your webserver like it’s always infected. Don’t do anything else important on it, and keep it segmented from your other computers with firewall rules.
Realistically no one is going to bother to hack you unless you’re posting shit that makes people angry. You’re mostly going to get prodded by bots looking for known vulnerabilities in Apache or the like, and you can stay protected with frequent updates.
If you’re hosting something dynamic or with code like PHP or something with user accounts and the like, then it’s slightly more complicated.