1

I just purchased a license key but that is for the production environment. How do I install and setup Expression Engine in my development server?

Improve this question

2 Answers 2

Reset to default
1

As long as you have a valid license, there is no issue with duplication. Just use the license for your development environment, and push it to the production environment. If you already have production set up, just clone the repo to your development environment.

EllisLab is not made up of monsters; many people run EE applications with a duplicated development/production set up. They know that. If you start using the license for different production environments, then you are violating your license in a way that can get you in trouble.

Concerned? You just gave them a bunch of money. Shoot them an email if you are really worried about it. I have a few things in the wild with a repository setup between development and production. To really avoid any possible issues, host your development install inside your production environment. 

https://www.example.com --> production install

https://www.example.com/dev --> development install

Then just set up your .gitignore file to ignore itself, and customize it for your dev and your production setup. It will take some time to setup right, but once it is right, you are golden.

Improve this answer
4
  • Thank you, I didn't know if having the license.key file in both environments would cause a failure (if EE "phoned-home" and saw two installs with the same license)
    – Don Rhummy
    Nov 5, 2015 at 1:40
  • It does phone home, but like I said, a good method is to have your development install inside of your production environment. There are many ways to go about it safely, and it makes it easier. Also, EllisLab are good people! Shoot them an email if you're worried.
    – jrothafer
    Nov 5, 2015 at 1:44
  • Unfortunately, it's not an option to put it inside the other. They're not located in the same hosts. One is internal.
    – Don Rhummy
    Nov 5, 2015 at 8:03
  • No need to worry about the internal one, then. I always understood one license per publically accessible site. Just secure your dev installation in a way that prohibits access from the outside (always a good idea) and Bob's your uncle.
    – Ingmar
    Dec 5, 2015 at 15:01
2

No worries anymore, as EE 5.x is open source and doesn't need a license.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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