Document the use of config/application.properties

Fixes: quarkusio#4452
geoand · Oct 9, 2019 · aad0aa7 · aad0aa7
1 parent ec07f7f
commit aad0aa7
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/docs/src/main/asciidoc/application-configuration-guide.adoc b/docs/src/main/asciidoc/application-configuration-guide.adoc
@@ -357,6 +357,11 @@ You can override these runtime properties with the following mechanisms (in decr
 2. using environment variables:
   * for a runner jar: `export QUARKUS_DATASOURCE_PASSWORD=youshallnotpass ; java -jar target/myapp-runner.jar`
   * for a native executable: `export QUARKUS_DATASOURCE_PASSWORD=youshallnotpass ; ./target/myapp-runner`
+3. using a configuration file placed in `$PWD/config/application.properties`
+  * By placing an `application.properties` file inside a directory named `config` which resides in the directory where the application runs, any runtime properties defined
+in that file will override the default configuration. Furthermore any runtime properties added to this file that were not part of the original `application.properties` file
+_will also_ be taken into account.
+  * This works in the same way for runner jar and the native executable
 
 NOTE: Environment variables names are following the conversion rules of link:https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configsources.asciidoc#default-configsources[Eclipse MicroProfile]