So you know how to do it securely and analyze what may go one when it is attacked. Or what else do you want with cybersecurity? It’s about securing services on the global network and local. And webhosting is one of those service.
So you know how to do it securely and analyze what may go one when it is attacked. Or what else do you want with cybersecurity? It’s about securing services on the global network and local. And webhosting is one of those service.
Depends on the support case you got. If it’s technical you have basically 24/7. I am in Germany but had once a hard drive failure in a server at 1am contacted technical support and it took about 30 minutes overall and the new drive was resilvering and the server back online. Takes a bit as the NOC needs to go to the data center and so on.
The problem is a lot of people here are beginners and have no real clue about network security. And opening a port is opening a door. If you have a bouncer that clears people beforehand then you can keep the door open. But you will still need to keep your bouncer trained so he can take care of people you don’t want. Same with software. Keep it updated and have security enhancements in place like 2FA and analysis tools like crowdsec or fail2ban. And the open port might not an issue at all.
But if you open a device like a NAS (cough QNAP cough) then you have a higher security risk.
TLDR; if you know what you are doing it might not have implications.
Moved on from compose ages ago. So should you.
I use rdiff-backup to backup the volumes directory of my VPS to a local machine via VPN. Containers are stored in some public registry anyways. Also use ansible with all the configurations and container settings.