shared hosting addon domains under public_html

[searain]

In the shared hosting. When I try to add a new domain, it would be default put the new domain's document_root under the /public_html. and the public_html is the document_root of the primary domain.

Now come up with my questions:

1. For example if I host 30 sites, according to the default set up, all these 30 sites are under /public_html, and all these 30 sites are in the sub-folder of the primary domain.
   
   So if one file of 1 site of these 30 sites get hacked, means one of the primary domain's file get hacked too. due to all of these sites are under the public_html (primary domain's document root).
   
   And if one of the primary domain's file get hacked, means that it is easy that from that security hole, other files of the primary domain may be hacked too. And due to all the 30 sites (addon domains) are just sub folders of the primary domain, then all the 30 sites are under risks too.
   
   In simple words, the default set up, all sites under public_html, if one site hacked, others sites would be easy to be hacked from that security break, am I right?
   
   Would it be better to put the new addon domain outside /home/my_user_name/public_html/? such as put the new site in /home/my_user_name/site1/, /home/my_user_name/site2 ...
   
   In this set up, even it is not bullet proof, but if site1 get hacked, it will be a little more difficult for hacker to hack site2 through site1's security break. Due to at least, they are not in the same document_root folder.
   
   I have asked hostgator tech support about this. I have no direct definitive answers. Some said that I cannot put site outside public_html (which he was wrong). some said I can put site outside public_html, some said if I put the site outsider public_html it would work but it might bring out some errors their tech support cannot support because i am not using the default set up.
   
   What is your opinion about should I put the site under public_html as it is default set up or should I put the new site out? from the view points of hostagor support staff or hostgator users?
2. If I put the site out of public_html, what set up changes I should do or what I should be aware, to avoid the errors that may happen due to that? in simple words, anything I should know if I put the site out of public_html?

[searain]

Could this thread be moved to shared hosting forum, that forum might be more suitable for this question? Thanks!

[slapshotw]

Searain-- have you considered moving to a reseller account, where all the domain files would be completely separate from each other?

[searain]

As a matter of fact. I am getting both accounts.

I have a reseller package so I can create each account for individual client.

And I also order a business account to host my own sites, my test sites, the sites under development etc. to use hostgator's unlimited space and bandwidth offer.

[searain]

As a matter of fact, in the reseller package, I need to create accounts, if I want to host multiple sites in one account, the default new addon domain is the same, will be put in the pulic_html of that the primary domain for that account I created. Same questions raised. Should I change the default set up and put the new addon domains outside of the public_html?

It seems put new addon in the public_html is the default set up of cpanel. Some people have questioned about this set up before like from one site to access the other sites easily etc.? Should this default set up be changed for the security reason? And if I change this set up, it seems the system allow it, what problems I may run into due to I change this set up?

[gwyneth]

I suggest looking for information in the cPanel forum. You'll have to join, but it's an invaluable resource for resellers.

[slapshotw]

Originally Posted by searain

As a matter of fact, in the reseller package, I need to create accounts, if I want to host multiple sites in one account, the default new addon domain is the same, will be put in the pulic_html of that the primary domain for that account I created.

The idea is, add each site as its own account. You can do that with the reseller, and because all sites will be running under a different server user, they won't have access to each others' files.