Score:0

Best way to isolate websites on Apache server

jm flag

I have read about multiple approaches on isolating websites on Apache server such that if one website is compromised, wont affect the rest nor the server itself. But I was confused and not sure which approach is the best in terms of security and usability?

Some of the approaches are:

  • Having every website in it's own Apache server in a docker container and using a proxy to map different requests to correspondent container port.
  • Have root as the owner of /var/www/(website dirs and files) and have apache group allowed to only read the files in /var/www/.
  • Enabling mod_users or mod_chroot in apache.
  • Using chroot jail.

Which is the best alternative? Is there a better alternative than the ones mentioned above?

vidarlo avatar
ar flag
There really isn't a *best*. Each of them have pros and cons. What makes sense depends on your scenario.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.