.. websites to use the folders:<BR><BR>C:InetpubDomainName.com<BR><BR>So, if you had:<BR>27Seconds.com<BR>Fishing.com<BR>Mouse.org< BR><BR>It would be:<BR>C:Inetpub27Seconds.com<BR>C:InetpubFishing. com<BR>C:InetpubMouse.org<BR><BR>But, that's just me.
This is one of the more common designs for smaller web servers.<BR>I would suggest putting the web sites on a separate drive, logical as well as physical.<BR>This way the data can be kept in case of a rebuild.<BR>Hardware redundancy is also a plus.
So, is InetPub a "special" folder that the system has to create or can I just create a folder basically anywhere I like?<BR>I ask this because I have a website which has the main web files in InetPubwwwroot. There is a database in InetPutdb. There are some email template text files in InetPubemails. All these folders make up the website as a whole and it's neat and tidy. If I put a new web site into InetPub the consequences of this is that the folders alongside wwwroot ("db" and "emails" folders) will be mixed in with folders for the additional website - which isn't a major problem but looks messy.<BR>The separate drive answer sounds like a good one but this isn't possible, I don't have an abundance of drives.<BR>I'd be interested to hear about anyone else's directory structure and if you know if there are "recommended" ways of structuring Windows web directories.
I see what you mean now.<BR>There is nothing special about INETPUB. Just something MS picked.<BR>Here is what i would recommend for you to do:<BR><BR>x:websites<BR><BR>x:websiteswebsite 1<BR>x:websiteswebsite 1public<BR>x:websiteswebsite 1emails<BR>x:websiteswebsite 1db<BR><BR>x:websiteswebsite 2<BR>x:websiteswebsite 2public<BR><BR>x:websiteswebsite 3<BR>x:websiteswebsite 3public<BR><BR>x:websiteswebsite 4<BR>x:websiteswebsite 4public<BR><BR>With this structure the web sites are separated and not all of their files are directly accessable via web browser (same as your current design).<BR><BR>Hope this works for you.