The big Question

[pixelpadre]

I am not asking anyone to change suit my needs.  I overcame the problem by simply using a fake domain (stupidfakedomain.com) that I do not own for the default user domain.  Then the public_html will never have any files.

There is no logical reason why creating an addon domain also creates an addon directory, but default domain does not get its own directory under the public_html directory.  Like you said, they all do it.  Its not a big problem, but its just chaotic when i explore my main domain and see all these other addon folders sorted alphabetically amongst my default domain files and folders.

[rcschaff]

Just out of curiosity, did you try creating add-on domains ../addondomain .   I don't use add-ons, so don't test it.

[pixelpadre]

Just out of curiosity, hows come you have a photo and I dont.

[rcschaff]

Cause I've got mad skills

[pixelpadre]

Cause I've got mad skills

You mean this?   http://www.madlibs.com/

[rcschaff]

Nope, Mad skills.  Cause my pictures my own, not a celeb.

[pixelpadre]

Thats a big assumption

[~Q~]

Good to know. Thank you.

Simple workaround.  Create an account with the domain localhost.localdomain.  << DOesn't server anything.  Addon domains now got to /public_html/mydomainname.com

Now public_html doesn't have to server any website.

Of course you could always create your own template for apache/nginx
Location of the files: /usr/local/cwpsrv/htdocs/resources/conf/web_servers/ | http templates = .tpl | https templates = .stpl |

Create a new template that points your main domain to public_html/(domian), and use that template for your website.   Custom templates will not get overwritten.