FR: Ability to store plugin license keys in .env file

[monachilada]

Description

For security reasons, it would be nice to be able to keep my plugin licenses stored in my .env files and out of the project.yaml file in my repo. Currently it's only possible to have the license defined explicitly in the project config file.

[brandonkelly]

This is possible with the CRAFT_LICENSE_KEY PHP constant.

.env:

LICENSE_KEY="#########..."

web/index.php (after loading .env):

define('CRAFT_LICENSE_KEY', getenv('LICENSE_KEY'));

[monachilada]

This is possible with the CRAFT_LICENSE_KEY PHP constant.

For the Craft license sure, but I was talking about specific 3rd party plugin licenses.

[brandonkelly]

Sorry, somehow I missed that!

[brandonkelly]

Just added the ability to set plugin license keys to environment variables using the $VARIABLE_NAME syntax, for the next release. If you do, they will be saved to your project.yaml file the same way, so the license key won’t make it into your repo.

[monachilada]

Fantastic, thank you!

[jurriaanr]

Small problem with this is that the name of the variable has a max length because the field is cut to the length of a license key

[brandonkelly]

@jurriaanr Thanks for pointing that out. Just removed the maxlength input attribute for today’s 3.2.6 release.

[janklan]

For those interested in storing the license key in an environment variable: don't forget to add define('CRAFT_LICENSE_KEY', getenv('LICENSE_KEY')); also to the /craft executable.

[khalwat]

FWIW, it does work already... I'm doing it here for Craft: https://github.com/nystudio107/devmode/blob/develop/cms/bootstrap.php#L23 and here for plugins: https://github.com/nystudio107/devmode/blob/develop/cms/config/project/project.yaml#L144