-
Hello there, We are (finally) migrating to Akka 2.10+ in our web application backed by Playframework. This version require the usage of a license-key that should be given via the configuration ( Unfortunately, we do have a strange behavior with that configuration. We can give it via the JVM options; Unfortunately, it seems that adding
However, we get a valid We do not create another actor system, we use the one from the Play Do you have any idea why did we get this message and how to fix it ? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
I have to double check, but without having time I wanted to share that I believe you have to set the config with a |
Beta Was this translation helpful? Give feedback.
-
To make this work in DEV mode ( PlayKeys.devSettings += "akka.license-key" -> "my-secrect-key" into The reason why you need to add this config via |
Beta Was this translation helpful? Give feedback.
To make this work in DEV mode (
sbt run
), you need to putinto
build.sbt
. Be aware, this is only picked up in dev mode, but not in production. When deploying your application in production, you still need to either set this key inapplication.conf
or supply it to the play app eg. via-D...
flag. You can find more details on how to supply configuration to your application in prod mode here: https://www.playframework.com/documentation/2.9.x/ConfigFileThe reason why you need to add this config via
PlayKeys.devSettings
in dev mode is because a Play app in dev mode works a bit different than when running in Production - in dev mode…