|
Chris Zander
|
October 7, 2016 at 9:54 am
Hi Guys, I have a uniques situation here maybe.
We moved out site to a new host and are working through a Development>Test>Live site system.
Normally I would consider only activating my key on the Live site ; however, the way the environment is managed, plugin updates one occur in the development side, then they have to migrate to “Test” and Then finally to “live”
The live site informs me that while I have a current support key it can only exist on one domain. It is currently on the DEV side I need it in all three. Ideas?
|
|
Josh
|
October 7, 2016 at 10:07 am
Hi Chris,
The key can only be activated on one site at any given time. An alternative that you can use is set up your Development site to use the Github hosted repository of EE4. You can set it to use the latest Master branch. That opens up two options, you either pull from github to get the latest, or you can use the github-updater plugin.
The other alternative is you set the key on the development site, then have a script that automatically removes the key from the options table on test and live right after a push.
|
|
Chris Zander
|
October 10, 2016 at 9:30 am
Since my development environment is where all plugin updates get managed anyway, is there any need to have the key on the other two environments?
|
|
Josh
|
October 10, 2016 at 11:13 am
Not only is there no need, but the key should not be used on the other two environments.
|
