I'm just getting to know how all this works, but I'm a bit confused. I have a Linux server going with Apache and ISPConfig installed. I'm just experimenting right now with setting up multiple domains on it. I tried to set up a test one using ISPConfig, but I don't think I did right. When I look in the /var/www directory to see the new website files, the directory it made was called "www.test site.com" I thought ISPConfig used the user name to make the home directory? When I look in the new site directory, I find: cgi-bin log phptmp ssl user web. I've been used to finding my regular web files under httpdocs, and secure files under httpsdocs. I guess I'm not as well read as I hoped I was on this. I need to find some examples of how to set things up using ISPConfig, and what the directory structure should be. If anyone has some advice, or can point me to a better help than the one on the ISPConfig site, it would be appreciated. Thanks.
No. ISPConfig creates a folder with the name web[ID] and a symlink www.domain.tld pointing to this folder for easier navigation on the shell. The html files must be put in the web folder for http and https (if enabled). There is nothing wrong with the directory structure.
Ok here's a follow up question. I set up a test site called www.testsite.com. If I look in /var/www I find: /apache2-default /sharedip /web1 /webalizer /www.testsite.com for directories. If I go to /www.testsite.com I find /cgi-bin /log /phptmp /ssl /user /web for directories. I get it that /web would be the web's root directory. But under /web1 I find: /cgi-bin /log /phptmp /ssl /user /web as well, just like under /www.testsite.com. So who's root files are those?
Those are the files and folder structure for your www.testsite.com. All website files go in the web folder. i.e. If you want to continue to set up a www.testsite.com, place the filesin /var/www/web1/web/. The other files and folders you referred to are ISPConfig 'control' files, and can be ignored.
