If you want to manage them as one site, then what you really have is one site with many sections and you should not use multi-tenancy. Instead, you would have maybe a custom theme provider that switches the theme based on what section of the site the user
Makes sense, but the mapping to multiple hostnames is what I'm trying to figure out options for. IOW, without multiple tenant, what's the closest thing to being able to create content at not just a relative path, but at a hostname + path?
The only thing I could think of so far was to make the hosts into folders, so the site would actually 'exist' and be managed as:
and then use URL rewrite so incoming urls are rewritten from http://host/path to http://localhost/host/path.
This seems like it would work, but I'm a little worried about it since that means having to rewrite outbound url's as well.
Having Orchard set up to more 'natively' handle the multiple hosts as separate content areas (but not completely separate like multi-tenant, since AFAICT that would make sharing things across hosts more difficult) I guess is the goal (although I'm not yet
familiar enough with Orchard to know if I'm even thinking of it the right way yet :)
Certainly custom code can make this work in multiple ways, but I'm trying to minimize how much is done custom (which is why multi-tenant is so attractive, as it's in the box and supported :)