Multi-Site Domain Names

[jwogrady]

With multi-company support, I'm trying to understand with multi-site why I can't do this....

 

https://storeone/portal/.....

 

https://storetwo/portal/.....

 

I've read this 

 

http://www.blesta.com/forums/index.php?/topic/3969-multi-company-questions/?p=29175

 

and this... 

 

http://docs.blesta.com/display/user/Creating+Companies

We suggest when using multi-company, you use subdomains for your Blesta installation, otherwise it will not be possible to have different website content at each hostname.

That statement, if true, may be a multi-site deal killer..   The reason is I need my product discussion to be on the main domain to support long-tail SEO.   Having the catalog on a subdomain really hurts SEO indexing.

 

I guess I could use www.  but man I hate www.

 

John

 

[itvietnam]

You could try it by request multi-company trial to test. No need setup on subdomain or subfolder also.

[serge]

yes, I confirm, you can use any domains you want, just do A records to point to IP of your Blesta install & edit/create in Blesta each company & their hostname, that's it

[Paul]

You could probably use aliases to have Blesta installed at /portal on each domain, and have different document roots for the primary sites. I'm not familiar with that in order to help you with it, but it should be possible to do. I like it clean and easy though, so we recommend sub-domains for Blesta installs if using multicompany.

[jwogrady]

Thanks for the replies, but I'm still not exactly clear on this issue. The suggestion of using subdomains is indeed clean but, I don't understand why domain name routing is insufficient.

 

Will this work?

 

https://example.com/portal

 

https://test.com/portal

 

From a marketing perspective, the only real option is to 301 everything to www or non-www.

[Paul]

Thanks for the replies, but I'm still not exactly clear on this issue. The suggestion of using subdomains is indeed clean but, I don't understand why domain name routing is insufficient.

 

Will this work?

 

https://example.com/portal

 

https://test.com/portal

 

From a marketing perspective, the only real option is to 301 everything to www or non-www.

 

That works certainly. But let's say the doc root is /var/www/html and you've added a directory called portal that Blesta is installed in. Now your website content would go into /var/www/html/ for BOTH sites. For most people, this is a problem because they want to have a different website at each domain. Either the application has to sort them out and display the correct website (I'm thinking something like Expression Engine multi-site) or the doc roots have to be different and /portal aliases to a separate location that Blesta is installed at.

 

You can see why using a subdomain is more convenient to configure.

[jwogrady]

Okay, I understand the issue much better now.  Still working on a solution... but at least I understand the use case we are talking about which is Blesta as standalone site.

 

I think my larger question is how to integrate Blesta into the rest of the site.  I'll post that as separate topic.