Yep its a option. Maybe a option for the database prefix as well.
It has always been like this, as far as I remember. Itâs controlled by the âInclude domain name in usernamesâ config option.
Since weâve had this enabled for decades, letâs also set âDomain name style in usernameâ to âFull domain name.â I find this to be the best default configuration for systems hosting multiple domains, where clashes are common.
Just look how clean and beautiful it looks:
I donât think anything could be better or cleaner for systems that host more than one domain! This looks splendid to me!
2 Likes
No I think we should leave Domain name style in username as it is. Since most systems arenât going to have domains that clash in the first component, this leads to shorter and easier to remember logins for domain owenrs.
@Jamie, consider creating the following, commonly expected set of top-level domains and subdomains:
company1.com
shop.company1.com
support.company1.com
company2.com
shop.company2.com
support.company2.com
To cause a clash, we donât need company1.com and company1.net; any name in a top-level domain will do, and itâs fairly easy to get.
Wouldnât company1.com, shop.company1.com and support.company1.com all be under the same owner though?
not on my server most sub domains are top level servers
Actually, no. At least not always, as itâs better to have a separate Unix user for each domain.