Skip to content
Permalink
Browse files

test comment in markdown

  • Loading branch information...
sherxon committed Jul 29, 2017
1 parent a5da977 commit 35645cc2a2a3b566ced4c364eb7927831086ff2c
Showing with 30 additions and 4 deletions.
  1. +30 −4 README.md
@@ -9,19 +9,45 @@ It includes:
[Service Discovery]() => Eureka by Netflix
[Sample Spring Boot Application]()

### Overview

I have added all above mentioned micro services into one parent project just to make it easy to manage in one place.
As it is just a POC project, it does not have much business logic abd heavy requirements. You can still run each
micro service independently in order.

Here are short overviews:

Config Server
[//]: # (This may be the most platform independent comment)
[comment]: <> (This is a comment, it will not be included)
[comment]: <> (in the output file unless you use it in)
[comment]: <> (a reference style link.)

##### Basics


### Config Server Overview:

Once we run our config server at default 8888 port, we can get all configs using following rules in json format.

**application** is the name of service defined by `spring.application.name` (also equal to `spring.cloud.config.name`) in config file.
**application** is the name of service defined by `spring.application.name` (or `spring.cloud.config.name`) in config file.
**profile** is the name of profiles set by `spring.profiles.active` on the client side , separated by comma
**label** is the label name to pull remote config files. if it is git label is _master_ by default
**label** is the label name to pull remote config files. if remote config location is git, the label is _master_ by default.

`/{application}/{profile}[/{label}]` such as http://localhost:8888/api-gateway/default
`/{application}-{profile}.yml`
`/{label}/{application}-{profile}.yml`
`/{application}-{profile}.properties`
`/{label}/{application}-{profile}.properties`

#### Tweaks
If you want to store remote config in filesystem, besides providing git repo url you should also use `spring.profiles.active.native` profile
#### Note
The followings are key points in configuration and management of config server. These are the ones
I had hard time figuring out in the beginning while building micro service architecture in the company.
There are might be some other and better solutions. Please pull request If you know one.


1. If you want to store remote config in filesystem,
besides providing file path: `spring.cloud.config.server.native.searchLocations=file:{path}`,
you should also use `spring.profiles.active=native` profile.
2.You can just add `spring.cloud.config.server.bootstrap=true` to bootstrap.yml of config server to tell config server to get
its configuration from remote file or repository on git.

0 comments on commit 35645cc

Please sign in to comment.
You can’t perform that action at this time.