Thread

Hello!

I’ve been using ExpressionEngine for our site, domain.com. Recently, we began expansion into Canada, and created the domain, domain.ca. Our reasoning for this was to allow our canadian partners to keep content separate from from the american site.

As I began setting up the MSM, I hit a road block when I tried to add the American developer site (dev.domain.com), the Canadian site (domain.ca), and the Canadian developer site (dev.domain.ca).

As per the license agreement of three domains, and msm restrictions, I cannot add the Canadian developer site. I’d like to know if there is a better way to set this up. Also, the more I think about it, the more I realize that under the license agreement, it’s technically one site spit into two languages. So I’m wondering if maybe I shouldn’t spread content across two domains.

Hi CRHain and welcome to the forums:)

You can buy extra sites for your MSM install for $49.95 Per Site from our store if you wish to do that.

When it comets to Multilanguage, yes there are 2 distinct routes to take. Deciding whether you are going to have different language versions of a site or whether you are going to translate content on the fly.

So either domain.ca or domain.com/ca/

There is some info regarding Multi language sites in our Wiki which may also influence your choice. It really depends on the type of content you have

Does that help?

Thanks John.

According to the MSM License, “One license grants a single ‘live’ installation in a production environment and ancillary ‘development use only’ installations as needed for that support the live installation (such as development and a staging servers).”

I’m looking to use two seats for a live site, and need two more for development, which should be included with my purchase. What is the best way to set this up so that I may seamlessly move from development to production. My initial thought was to simply build my templates on the development site, then copy over the templates when ready. I can’t do that, however, if I can’t build the second development site. Thanks for your help.

CRHain,

The license allows you to set up your development servers to best suit your needs, as long as that server is not publicly accessible. Once development is complete, you can migrate that site to live production. “Not publicly accessible” could be as simple as making a temporary index.html file to explain the site is in development. Then you would rename index.php to index_dex.php for example. Please note, that whatever you choose to rename index.php needs to be reflected in your Control Panel. To do that, you would navigate to Admin-> General Configuration and set “Name of your site’s index page” to match your renamed index.php.

Does this help clarify the situation for you?

Best,

Okay, thank you. I’ll keep that in mind.

I’ve since looked into a local development environment. So far so good.

Just for reference, won’t changing the CP to index_dex.php in the control panel take my site offline?

Hi CRHain,

You’d have to know to access the development version at index_dex.php. EE is pretty flexible; itll be up to you as far as what makes the most sense for your development workflow.

Is everything working as expected at this point?

Yes, I found a comfortable solution using local hosting. Someday in the future I might look into other methods, but right now, this is what makes most sense to me.

Thank you.

Excellent! And don’t hesitate to post again if anything else comes up.