We have a very simple development process, and I believe this process has messed up the license.

app-client.local.mycompany.com.br => developer environment (intranet only)
app-client.qa.mycompany.com.br => quality insurance environment (openshift)  (intranet only)
app-client.hom.mycompany.com.br => client test environment (openshift) (intranet only,client access via vpn)
something.com.br => client website

local/qa/hom I'm using "environment = dev", but somehow local is working but qa and hom is not.

The database is a copy =>

  • from local to qa/hom when is a website in development
  • from prod to local/qa/hom when it is an already made website

It means every environment has its own database.

How to proceed to use dev licensing at local/qa/hom ?


A few pre-requisites:

  1. A Craft purchase/edition is tied to the craft/config/license.key file that is in place at the time the purchase is made and wherever that file goes, the purchase/edition will follow.

  2. A craft/config/license.key file can only be tied to one "public" domain at a time.

  3. Craft license validation doesn't run on "non-public" domains and you're able to trial the different editions of Craft for as long as you want on non-public domains.


Craft will treat app-client.local.mycompany.com.br as a "non-public" domain, because it has one of the keywords we're looking for in its own segment in the subdomain. You can see a list of those keywords here in number 4 of the previous link.

The rest of those domains Craft treats as "public" because they don't match any of the rules in that link, so license validation will run on them.

You don't say exactly what you're issue is, but if you purchased Craft on the development domain and you're using that same license.key file on the three other public domains, you're probably getting a warning in the Control Panel saying that license is already in use on another domain.

Since they are all for the same "site", you can either tell everyone that has access to the Control Panel to ignore the message and to not transfer the license away from the production domain, or you can change your qa and hom domains so Craft treats them as "non-public" and license validation won't run.

More related reading: https://craftcms.com/support/license-key-info

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.