Is there a possibility to use a local application.conf with Play 1.2.5? Our problem is that different developers have somewhat different setups that we don’t want to save to version control.
Alternatives found:
- Just modifying application.conf
- Have to be careful not to commit changes to VCS
- Environments : Own environment for each developer : %john, %mary (saved to VCS)
- OK alternative, even though we woudn’t like to save those to version control
- We have do change those during development every now and then -> would cause unnecessary changes
- @include : application.conf option for additional configuration files
- Play 1.2.5 documentation : This is an experimental feature that does not yet work properly. 🙁
Something else?
Especially, is there a way to tell Play to use custom file name (as “conf/application.conf.local” instead of default “conf/application.conf”?
I just encountered Play 1.x module externalconfig that could help. Seems to work for our purposes. As an extra, this helps to keep production passwords etc out from the VCS.
Note that this module works only within Play’s Java code – Play modules implemented in Python (as migrate, for example) won’t be aware of external configuration. There might be concerns also with other Java modules that rely on
onConfigurationRead().