Env specific settings override mechanisms

Lagom services may need specific settings depending on the environment (test, dev, prod).

It may be useful to introduce production.conf and development.conf that override application.confonly on the mentioned environment.

E.g. using the DevMode Cassandra server during development but production environment needs specific tuning to use an externally provided Cassandra. In that case, most settings would be in application.conf but Production env needs SessionProvider override and contact-points.

[jroper]

While yes it’s simple to achieve:

a) We don’t have instructions for the above - for example, where do you add the -Dconfig.resource argument? b) Lagom is by design a lot more opinionated than Play, and this is possibly one place where that opinionatedness should show - we should have a supported, consistent way of providing different configurations in different environments.

[guizmaii]

Hi

Just for information, here is how we achieve this in our Play apps but also in our Lagom app until now, in the build.sbt:

// Debug helper
bashScriptExtraDefines += """echo "ENV = ${ENV}""""

bashScriptExtraDefines += """addJava "-Dconfig.resource=${ENV}.conf""""
bashScriptExtraDefines += """addJava "-Dnewrelic.environment=${ENV}""""

It works well but I think that to give an “official” solution to achieve that will help beginners !