application.properties, e.g.
application.properties
server.port: 8888
-spring.cloud.config.server.git.uri: file://${HOME}/config-repo
+spring.cloud.config.server.git.uri: file://${user.home}/config-repo
diff --git a/spring-cloud.html b/spring-cloud.html index b7a1c1b..84db7f3 100644 --- a/spring-cloud.html +++ b/spring-cloud.html @@ -1085,9 +1085,9 @@ $ mvn spring-boot:run
The server is a Spring Boot application so you can build the jar file
-and run that (java -jar …) or pull it down from a Maven
-repository. Then try it out as a client:
The server is a Spring Boot application so you can run it from your
+IDE instead if you prefer (the main class is
+ConfigServerApplication). Then try it out a client:
application.properties, e.g.
server.port: 8888
-spring.cloud.config.server.git.uri: file://${HOME}/config-repo
+spring.cloud.config.server.git.uri: file://${user.home}/config-repo
where ${HOME}/config-repo is a git repository containing
+
where ${user.home}/config-repo is a git repository containing
YAML and properties files.
FooConfiguration has to be @Configuration but take care that it is not in a @ComponentScan for the main application context, otherwise it will be shared by all the @FeignClient`s. If you use `@ComponentScan (or @SpringBootApplication) you need to take steps to avoid it being included (for instance put it in a separate, non-overlapping package, or specify the packages to scan explicitly in the @ComponentScan).
+The FooConfiguration has to be @Configuration but take care that it is not in a @ComponentScan for the main application context, otherwise it will be used for every @FeignClient. If you use @ComponentScan (or @SpringBootApplication) you need to take steps to avoid it being included (for instance put it in a separate, non-overlapping package, or specify the packages to scan explicitly in the @ComponentScan).