How do you structure your web server?
MossyBlog is asking about how people setup their new web servers. I though I'd post my thoughts on directory structure here.
This is web server directory structure that I have used for long time (probably 6 or 7 years). A former co-worker Eric Griff helped me come up with it I believe.
We wanted a directory structure that would allow us to keep domains grouped together, so if you have domain.com, and blog.domain.com the will be located near each other. Also we wanted there to be room to put things related to the domain above the web root such as logs, documentation, and at the time we used access, so we also had a directory for the database files. I haven't used access in years so I leave that one out now.
So here's what it looks like:
/websites/domain.com/www/web/ (this is your web server root for www.domain.com) /websites/domain.com/www/logs/ (logs go here) /websites/domain.com/www/docs/ (docs) /websites/domain.com/www/db/ (database files, optional) /websites/domain.com/www/requirements.txt
requirements.txt is a file where you can put any server requirements that the site has, I usually list what datasources, custom tags, or server components the site requires in this file. Then if I want to move it to another server you know what you need to install to get the site working.
Now when you setup another site under that domain, such as blog.domain.com, it would look like this:
/websites/domain.com/blog/web/ (web root for blog.domain.com) /websites/domain.com/blog/logs/ (logs go here) ...
So that's how I setup my directories, how do you do it?
Like this? Follow me ↯Tweet Follow @pfreitag
How do you structure your web server? was first published on July 26, 2005.