|
|
@ -496,8 +496,9 @@ On your application classpath (for example, inside your jar) you can have an `ap
|
|
|
|
When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`.
|
|
|
|
When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`.
|
|
|
|
For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`).
|
|
|
|
For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`).
|
|
|
|
|
|
|
|
|
|
|
|
NOTE: The `env` and `configprops` endpoints can also be useful in determining why a property has a particular value.
|
|
|
|
TIP: The `env` and `configprops` endpoints can be useful in determining why a property has a particular value.
|
|
|
|
You can use these two endpoints to diagnose unexpected property values.
|
|
|
|
You can use these two endpoints to diagnose unexpected property values.
|
|
|
|
|
|
|
|
See the "<<production-ready-features.adoc#production-ready-endpoints, Production ready features>>" section for details.
|
|
|
|
|
|
|
|
|
|
|
|
Spring Boot also supports wildcard locations when loading configuration files.
|
|
|
|
Spring Boot also supports wildcard locations when loading configuration files.
|
|
|
|
By default, a wildcard location of `config/*/` outside of your jar is supported.
|
|
|
|
By default, a wildcard location of `config/*/` outside of your jar is supported.
|
|
|
|