https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop<p>Dear Ivy team</p> <p>Is it possible to pass the Ivy license via env prop ? </p> <p>Reason for my question : as you might know we in KLARA want to build our own image. If the license has to be provided as a file in a certain directory then our image, which is hosted somewhere in the cloud, contains the license. May be not so nice from your point of view.</p> <p>The idea is that we store the license as a secret and inject it at startup of the image.</p> <p>Regards John</p>enThu, 03 Oct 2019 11:45:11 -0400https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop#4062<p>We have general approach. The licence can now be provided over the configuration key Licence. Like all other configurations you can provided it via ENV, secrets or even in ivy. yaml. (your inital requirement was about ENV). </p> <p>Why you can not provide it in the configuration directory?</p>Alex SuterThu, 03 Oct 2019 11:45:11 -0400https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop#4062https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop#4053<p>Hi Alex</p> <p>I think it should not be necessary. With secret and mountPath / volumes it should be possible to pass the license to Ivy. Unfortunately it does not work if the license has to be in the root folder of Ivy. See my other post.</p> <p>Regards John</p>John MoserThu, 03 Oct 2019 08:24:16 -0400https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop#4053https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop/4000<p>Thank you very much for this idea. We will provide a configuration key where you can pass the licence file in. Then you can provide it as Environment-Variable or as (Docker/Container)-Secret. This will be available in ivy 8.0.</p>Alex SuterThu, 19 Sep 2019 05:10:08 -0400https://answers.axonivy.com/questions/3999/docker-pass-ivy-license-as-env-prop/4000