Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Do to some changes in personel at my company I have inherited the responsability over administering our web server. Unfortunately there does not seem to have been a standard convention used for setting up website directories.

I was thinking of organizing the website as follows:

D:\inet[CustomerName]\wwwroot\[WebsiteDomainName]

But I was curious if any of you had a better convention or could recomend a best practice for how website directories should be organized.

Thank you

share|improve this question
add comment

4 Answers 4

Generally I use

\user
\user\domain
\user\domain\logs    # Location of the webserver logs
\user\domain\public  # Publicly accessible directory

If using a dynamic website, I often put the majority of the files within subfolders under \user\domain\ outside of the public directory.

share|improve this answer
    
I'm interested in beign able to capture whom the website is hosted for. We design many microsites for our clients so its nice if we can include the client name as a part of the directory structure. We use 3 letter abbreviations for our client codes. What do you think of \user\companycode\domain format. Is there any possible disadvantage to using this naming convention. –  David Negron May 7 '09 at 23:19
    
Heh sorry for the wall of text but I just realized something could the value you have as user be actually the company name. Please forgive my naiveness. –  David Negron May 7 '09 at 23:21
add comment

Honestly, use whatever works best for you. Pick a system and stick with it, document it, and make sure that everyone who would ever need to make changes is aware of it and why it is important to stick with the standard.

Edited to include our standard folder structure (for www.example.com):

[drive]:\Inetpub\wwwroot\example.com\docs

We use a 'docs' folder for the web site as some clients also have separate FTP storage space which we put into a 'storage' folder under their domain name folder.

share|improve this answer
1  
Oh I agree that it's up to me to pick something. But since web site administration is not part of my usual skill set. I figuired I might see if there were any pain points that I should avoid. I'm primaraly a software developer so I'm all about finding best practices and adopted conventions. –  David Negron May 7 '09 at 23:42
add comment

I work for the county government, where some departments have multiple applications, so our structure is as follows:

D:\wwwdata\DEPTCODE\APPNAME

IIS has virtual directories configured appropriately, which allows us to give more accessible application names (such as countynetapps\eaf). Each application has an "Output" folder which is the only writable folder for the application iteself, for security purposes.

Naturally there are exceptions to various scenarios, but this setup works for nearly all of our apps.

share|improve this answer
add comment

I keep Inetpub as the root, and end up with something like:

D:\Inetpub\wwwroot (Default Web Site)
D:\Inetpub\exampleroot (www.example.com)
D:\Inetpub\sampleroot (www.sample.com)

If I was worried about grouping multiple sites under a user or department, I'd just add it after Inetpub.

That keeps the D:\ available for other things without co-mingling the web stuff. Also, I never like sharing the root directory (no particular reason, it just annoys me).

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.