From e6a99adb018e9a2dcbb2afa4df3ea2f6be61e01a Mon Sep 17 00:00:00 2001 From: Ryan Baxter Date: Thu, 6 Apr 2017 20:06:40 -0400 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud-config.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-cloud-config.html b/spring-cloud-config.html index 072f37e9..51f34920 100644 --- a/spring-cloud-config.html +++ b/spring-cloud-config.html @@ -462,7 +462,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
-

1.3.0.BUILD-SNAPSHOT

+

1.3.0.RELEASE

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.