20:31
What's a more common way to organize docroots?
I'm implementing a new webserver, and the original directory structure would be
/us/web/http/example.com, /us/web/http/a.example.com, /us/web/https/secure.example.com, etc
However I'm thinking now that both http and https should always always serve the same sites.
So I'm considering using simply /us/web/example.com, /us/web/sub.example.com, etc.
If example.com exists and www.example.com does not, users are automatically redirected to example.com.
If www.example.com exists and example.com does not, users are automatically redirected to www.example.com. (although this one is going to be much less common)
The only issue I see with this directory structure is that alphabetically sorting the directories isn't great.
However, I didn't see a good way to file sub.example.com within example.com.
Nor did I want to use com.example.sub.
Nor did I like example.com~sub...
Before I move on /us/web/example.com, /us/web/sub.example.com I was wondering what's most common?
Do folks usually have domains organized under a web folder in this way, or is it usually on a 'webserver instance' or other filing system?
I realize some folks use a separate VM per site but I'm no interested in that.
