Supports environment and application config in an opinionated way.
The application config is loaded from the name specified in the classpath.
Eg if the app name is "foo" then the application conf is foo.conf and this must
exist on the classpath at /foo.conf
The environment config is loaded from a file called $env.conf where env is determined
from a sys property called CONFIG_ENV. If no env is found, it will default to LOCAL.
The $env.conf file will be searched for the following places, with the first match winning:
- current working directory (cwd)
- users home folder
- classpath
Finally an override.conf can be located in the cwd only.
The order of priority, highest at the top:
./override.conf
./${env}.conf or ~/${env}.conf or classpath:${env}.conf
classpath:${application}.conf
classpath:reference.conf (all reference.conf files on the classpath are merged into a single file)
Supports environment and application config in an opinionated way.
The application config is loaded from the name specified in the classpath. Eg if the app name is "foo" then the application conf is foo.conf and this must exist on the classpath at /foo.conf
The environment config is loaded from a file called $env.conf where env is determined from a sys property called CONFIG_ENV. If no env is found, it will default to LOCAL. The $env.conf file will be searched for the following places, with the first match winning: - current working directory (cwd) - users home folder - classpath
Finally an override.conf can be located in the cwd only.
The order of priority, highest at the top: ./override.conf ./${env}.conf or ~/${env}.conf or classpath:${env}.conf classpath:${application}.conf classpath:reference.conf (all reference.conf files on the classpath are merged into a single file)