I’ve been wanting to make the switch to CommandBox for a while now, but I’ve stuck with IIS because it’s what I know and I haven’t taken the time to figure out if CommandBox can handle our particular setup.
We have a website that supports over a thousand subdomains - think abc.site.com, xyz.site.com, etc. The application reads the subdomain and each one acts as its own independent site with different catalogs and content. This makes it really easy to replicate specific site issues locally when we need to debug.
What I’m wondering is whether CommandBox can handle this kind of multi-subdomain setup where I could spin up the server and hit actual domains like xyz.site.com or xyz.site.local. Can this be done through config files, or am I better off just sticking with running the CFML engine locally through IIS?
I know this is pretty vague without more technical details, but I wanted to throw this out there first to see if anyone thinks this is even a viable path before I dive deeper into the specifics.
Actually, re-reading your message, let me clarify. I assumed that you have a different web root for each domain. If this is not the case and you have only a single web root and simply point all the domains at the same site, then you can completely disregard the multi-site docs. In single site mode, the host name actually isn’t used at all. The site is simply bound to the IP address, and all traffic is routed to that site/web root regardless of the host header. In that case, you simply need to have DNS set up for each domain to point to the same IP and you’re good. If you have more than one SSL cert to configure, that is no issue as well. Whether using one site or multi sites, you can configure as many SSL certs as you like on an HTTPS binding and we’ll use SNI to match the correct cert based on the incoming host header.