<commit_before>Start the server:

----
$ cd spring-cloud-config-server
$ ../mvnw spring-boot:run
----

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 out a client:

----
$ curl localhost:8888/foo/development
{"name":"development","label":"master","propertySources":[
  {"name":"https://github.com/scratches/config-repo/foo-development.properties","source":{"bar":"spam"}},
  {"name":"https://github.com/scratches/config-repo/foo.properties","source":{"foo":"bar"}}
]}
----

The default strategy for locating property sources is to clone a git
repository (at `spring.cloud.config.server.git.uri`) and use it to
initialize a mini `SpringApplication`. The mini-application's
`Environment` is used to enumerate property sources and publish them
via a JSON endpoint.

The HTTP service has resources in the form:

----
/{application}/{profile}[/{label}]
/{application}-{profile}.yml
/{label}/{application}-{profile}.yml
/{application}-{profile}.properties
/{label}/{application}-{profile}.properties
----

where the "application" is injected as the `spring.config.name` in the
`SpringApplication` (i.e. what is normally "application" in a regular<commit_msg>[Honglai] fix readme typo (#748)<commit_after>Start the server:

----
$ cd spring-cloud-config-server
$ ../mvnw spring-boot:run
----

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 out a client:

----
$ curl localhost:8888/foo/development
{"name":"foo","label":"master","propertySources":[
  {"name":"https://github.com/scratches/config-repo/foo-development.properties","source":{"bar":"spam"}},
  {"name":"https://github.com/scratches/config-repo/foo.properties","source":{"foo":"bar"}}
]}
----

The default strategy for locating property sources is to clone a git
repository (at `spring.cloud.config.server.git.uri`) and use it to
initialize a mini `SpringApplication`. The mini-application's
`Environment` is used to enumerate property sources and publish them
via a JSON endpoint.

The HTTP service has resources in the form:

----
/{application}/{profile}[/{label}]
/{application}-{profile}.yml
/{label}/{application}-{profile}.yml
/{application}-{profile}.properties
/{label}/{application}-{profile}.properties
----

where the "application" is injected as the `spring.config.name` in the
`SpringApplication` (i.e. what is normally "application" in a regular
{'fraction_non_alphanumeric': 0.1598571995239984, 'fraction_numerical': 0.00436334787782626, 'mean_word_length': 4.878787878787879, 'pattern_counts': {'":': 18, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '395845', 'n_tokens_mistral': 732, 'n_tokens_neox': 692, 'n_words': 227}