We currently have a single site hosted on GoDaddy (shared linux) and running ModX Revo v2.0.4-pl2. We are working on getting it upgraded (finally!) and fixing some bugs, but before we got too far we wanted to make sure we are setup for multiple domains.
We will be porting over additional unrelated domains for hosting on our shared linux box. Moreover, one of the sites we will be porting over uses a custom CMS so we need the flexibility to not run every site on ModX.
I don't have a lot of experience with contexts and am trying to understand my options here. Is there any reason why I would install multiple instances of ModX versus using contexts for each domain?
I understand why a subdomain would share a single installation through contexts (e.g. webstore.domain.com and domain.com), but it seems like it would be cleaner to manage unrelated domains with individual ModX packages.
Your advice is greatly appreciated, thank you!
[ed. note: lessh2o last edited this post 10 years, 8 months ago.]
I usually avoid contexts if at all possible. I think you're correct that having separate MODX installs will be easier. You'll have to make sure to create a separate database for each site.
Contexts make sense if the sites will share a lot of things (e.g., sites that are identical except for the language used).
In other cases, the only advantage of using a single site with contexts is when it's time to upgrade MODX, since you have to upgrade each site separately when they are independent installs. Now that the UpgradeMODX extra exists, that's not nearly as important.
Thanks BobRay, I think you confirmed what I was thinking - that contexts are more of a pain than they're worth unless the websites are very closely related (i.e. subdomains for different parts of a single entity's website).
Is there anyone out there willing to make a case for contexts?
Right now my plan is to have a unique instance of ModX for each domain, as well as a separate install for each development site subdomain.
-
☆ A M B ☆
- 24,524 Posts
Of course, your biggest problem is trying to do anything interesting with Revo on a GoDaddy server. That hosting is notorious for not playing well with MODX.
Hah, fair enough sottwell. What would you recommend instead? InMotion? Bluehost? What's the best mainstream host for ModX Revo?
-
☆ A M B ☆
- 24,524 Posts
I use SkyToaster - very active in the MODX community, excellent support, and their own site is on Revo. However, to be fair, there are others.
http://bobsguides.com/modx-friendly-hosts.html
By the way, you might be interested in joining the Slack community.
http://modx.org/
If the unrelated domains are for unrelated clients, then I'd presume the clients would need access to the CMS - in which case you'd go for separate MODX installs.
If you are running a client's website where there are completely different URLs for different for different 'brands' within the client's service / product portfolio, then using different contexts can work well, as the client can administer everything with one log in. They sometimes like that.
GoDaddy - we have used their hosting for Modx where the client is with them already. It works ok - bit of a pain using their control panel and hunting down settings, but it's doable
