QNAP Web Server versus using a Container

[dsnider]

I tried to search for this, but could not find it, so please forgive me if this has already been asked...

I would like to know the pros and cons of using the QTS Web Server to host websites versus setting up a container to do the same thing.

Is there a benefit to containerization in this instance (security, stability, resource management, QoS, etc) or would it not be worth the added effort?

I was thinking of the example of a WordPress site. I know this can be done entirely at the top QTS level, and that you could also set up a container with a LAMP stack (Linux Apache, MySQL, PHP) and install WordPress there and keep it all completely segregated from QTS.

Has anyone done a comparison between both methods?

Thanks in advance!

[dolbyman]

QNAP webserver is outdated and runs as admin, a VERY bad idea to host any public websites on your NAS (just next to exposing your web interface to WAN)

No need for a whole LAMP container .. there is ready to go YAML compose scripts for wordpress.

[dsnider]

So even using a container, you'd say that it's dangerous to run a public website on your NAS? What if you used something like Cloudflare in front of it?

[dolbyman]

A container is 'containerized' so it's not as risky, no.

If you want to go through lengths of signing up for cloudflare, maybe spend a few bucks a year for a web hosting service (that way a hacked website does not infect your LAN)