diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc index 3eb1af6419..be9a1121fa 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc @@ -916,7 +916,11 @@ NOTE: Profiles activated in the above files will not affect the loading of < ---- -Then you need to set a configprop:spring.devtools.remote.secret[] property, as shown in the following example: - -[source,properties,indent=0,configprops] ----- - spring.devtools.remote.secret=mysecret ----- - -WARNING: Enabling `spring-boot-devtools` on a remote application is a security risk. -You should never enable support on a production deployment. +Then you need to set the configprop:spring.devtools.remote.secret[] property. +Like any important password or secret, the value should be unique and strong such that it cannot be guessed or brute-forced. Remote devtools support is provided in two parts: a server-side endpoint that accepts connections and a client application that you run in your IDE. The server component is automatically enabled when the configprop:spring.devtools.remote.secret[] property is set.