From c2160ac5201e3b8a863921062eac22e3679b9e89 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Fri, 9 Nov 2018 21:59:27 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__embedding_the_config_server.html | 4 ++-- single/spring-cloud-config.html | 4 ++-- spring-cloud-config.xml | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/multi/multi__embedding_the_config_server.html b/multi/multi__embedding_the_config_server.html index 39187b6a..11c11da4 100644 --- a/multi/multi__embedding_the_config_server.html +++ b/multi/multi__embedding_the_config_server.html @@ -3,11 +3,11 @@ 5. Embedding the Config Server
5. Embedding the Config Server
Prev   Next

5. Embedding the Config Server

The Config Server runs best as a standalone application. However, if need be, you can embed it in another application. To do so, use the @EnableConfigServer annotation. -An optional property named spring.cloud.config.server.bootstrap can be useful in this case is. +An optional property named spring.cloud.config.server.bootstrap can be useful in this case. It is a flag to indicate whether the server should configure itself from its own remote repository. By default, the flag is off, because it can delay startup. However, when embedded in another application, it makes sense to initialize the same way as any other application.

[Note]Note

If you use the bootstrap flag, the config server needs to have its name and repository URI configured in bootstrap.yml.

To change the location of the server endpoints, you can (optionally) set spring.cloud.config.server.prefix (for example, /config), to serve the resources under a prefix. The prefix should start but not end with a /. It is applied to the @RequestMappings in the Config Server (that is, underneath the Spring Boot server.servletPath and server.contextPath prefixes).

If you want to read the configuration for an application directly from the backend repository (instead of from the config server), you -basically wat an embedded config server with no endpoints. +basically want an embedded config server with no endpoints. You can switch off the endpoints entirely by not using the @EnableConfigServer annotation (set spring.cloud.config.server.bootstrap=true).

Prev   Next
4. Serving Plain Text Home 6. Push Notifications and Spring Cloud Bus
\ No newline at end of file diff --git a/single/spring-cloud-config.html b/single/spring-cloud-config.html index 65c6695f..c320031a 100644 --- a/single/spring-cloud-config.html +++ b/single/spring-cloud-config.html @@ -545,13 +545,13 @@ So, if you want a profile-specific file, /*/development/*/ So, the preceding example for the default profile could be /foo/default/nginx.conf?useDefaultLabel.

5. Embedding the Config Server

The Config Server runs best as a standalone application. However, if need be, you can embed it in another application. To do so, use the @EnableConfigServer annotation. -An optional property named spring.cloud.config.server.bootstrap can be useful in this case is. +An optional property named spring.cloud.config.server.bootstrap can be useful in this case. It is a flag to indicate whether the server should configure itself from its own remote repository. By default, the flag is off, because it can delay startup. However, when embedded in another application, it makes sense to initialize the same way as any other application.

[Note]Note

If you use the bootstrap flag, the config server needs to have its name and repository URI configured in bootstrap.yml.

To change the location of the server endpoints, you can (optionally) set spring.cloud.config.server.prefix (for example, /config), to serve the resources under a prefix. The prefix should start but not end with a /. It is applied to the @RequestMappings in the Config Server (that is, underneath the Spring Boot server.servletPath and server.contextPath prefixes).

If you want to read the configuration for an application directly from the backend repository (instead of from the config server), you -basically wat an embedded config server with no endpoints. +basically want an embedded config server with no endpoints. You can switch off the endpoints entirely by not using the @EnableConfigServer annotation (set spring.cloud.config.server.bootstrap=true).

6. Push Notifications and Spring Cloud Bus

Many source code repository providers (such as Github, Gitlab, Gitea, Gitee, Gogs, or Bitbucket) notify you of changes in a repository through a webhook. You can configure the webhook through the provider’s user interface as a URL and a set of events in which you are interested. For instance, Github uses a POST to the webhook with a JSON body containing a list of commits and a header (X-Github-Event) set to push. diff --git a/spring-cloud-config.xml b/spring-cloud-config.xml index 987c05c5..1b70b0a4 100644 --- a/spring-cloud-config.xml +++ b/spring-cloud-config.xml @@ -1133,7 +1133,7 @@ So, the preceding example for the default profile could be The Config Server runs best as a standalone application. However, if need be, you can embed it in another application. To do so, use the @EnableConfigServer annotation. -An optional property named spring.cloud.config.server.bootstrap can be useful in this case is. +An optional property named spring.cloud.config.server.bootstrap can be useful in this case. It is a flag to indicate whether the server should configure itself from its own remote repository. By default, the flag is off, because it can delay startup. However, when embedded in another application, it makes sense to initialize the same way as any other application. @@ -1144,7 +1144,7 @@ However, when embedded in another application, it makes sense to initialize the The prefix should start but not end with a /. It is applied to the @RequestMappings in the Config Server (that is, underneath the Spring Boot server.servletPath and server.contextPath prefixes). If you want to read the configuration for an application directly from the backend repository (instead of from the config server), you -basically wat an embedded config server with no endpoints. +basically want an embedded config server with no endpoints. You can switch off the endpoints entirely by not using the @EnableConfigServer annotation (set spring.cloud.config.server.bootstrap=true).