Skip to main content

Sites in Root or Public_html?

Comments

3 comments

  • Eminds
    Well the scenario you have mentioned can be done however you will have to work alot on permissions hence storing the websites in public_html is the folder where the webfiles has to be placed. Regarding the approach you have mentioned, I don't think there are any strategic drawbacks.
    0
  • Eladnova
    Well the scenario you have mentioned can be done however you will have to work alot on permissions.

    Thank you for answering @Eminds Would you mind giving me an example of potential permissions problems. Are these permission issues for general front end views of the site? Currently I've setup host access and can connect to the site and database fine.
    0
  • cPWilliamL
    Hi @Eminds [QUOTE]Would you mind giving me an example of potential permissions problems
    Perhaps they are referencing WHM > Tweak Setting " Restrict document roots to public_html"(publichtmlsubsonly). If you are not restricted to 'public_html', I'd recommend using the account's homedir(e.g. /home/username/addon.com/). This provides a bit better segregation, which can be very helpful in the event of a compromise. Should everything be placed in 'public_html', one site compromise would very likely result in all sites littered with malware. It's still possible that additional domains placed in the user's homedir could be infected from other addon domains within the same account; however, it is less likely.
    0

Please sign in to leave a comment.