Revert & fix "fix docs for setting profiles"

Adjustment to documentation wording
This commit is contained in:
Frank Migliorino 2019-09-24 10:54:47 -04:00
parent 1e2fbb97b0
commit 343175c64c

View file

@ -22,16 +22,15 @@
scripts (or set "spring.datasource.initialization-mode=always" the first time you run the app). scripts (or set "spring.datasource.initialization-mode=always" the first time you run the app).
3) Run the app with `spring.profiles.active=mysql` (e.g. as a System property via the command 3) Run the app with `spring.profiles.active=mysql` (e.g. as a System property via the command
line, but any way that sets that property in a Spring Boot app should work). line, but any way that sets that property in a Spring Boot app should work). For newer versions
of Spring Boot, those will fork the JVM that executes the webserver, which means properties on
the command line are lost. Use
4) For newer versions of Spring Boot, those will fork the JVM that executes the webserver,
which means properties on the command line are lost. You can use:
mvn spring-boot:run\ mvn spring-boot:run\
-Dspring-boot.run.jvmArguments="-Dspring.profiles.active=mysql -Dspring.datasource.initialization-mode=always" -Dspring-boot.run.jvmArguments="-Dspring.profiles.active=mysql"
To set profiles & properties. To make mysql work with forking.
N.B. the "petclinic" database has to exist for the app to work with the JDBC URL value N.B. the "petclinic" database has to exist for the app to work with the JDBC URL value
as it is configured by default. This condition is taken care of by the docker-compose as it is configured by default. This condition is taken care of by the docker-compose
configuration provided, or by the `schema.sql` if you can run that as root. configuration provided, or by the `schema.sql` if you can run that as root.