Spring Cloud Launcher
Building
./mvnw clean install from parent directory
Installing
Running
$ spring cloud
Currently starts configserver, dataflow, eureka, h2 (db server) and kafka. Here is the full configuration.
Configuring
Spring Cloud Launcher uses normal Spring Boot configuration mechanisms. The config name is cloud, so configuration can go in cloud.yml or cloud.properties.
For example, to run configserver and eureka, create a cloud.yml that looks like:
spring:
cloud:
launcher:
deployables:
- name: configserver
coordinates: maven://org.springframework.cloud.launcher:spring-cloud-launcher-configserver:1.2.1.RELEASE
port: 8888
waitUntilStarted: true
order: -10
- name: eureka
coordinates: maven://org.springframework.cloud.launcher:spring-cloud-launcher-eureka:1.2.1.RELEASE
port: 8761
The name attribute is required. If waitUntilStarted is true, Launcher will block until the application has reached the deployed state. Before commands are deployed, the list is sorted using Spring's OrderComparator. In the above case, configserver is deployed before any other app is deployed. Currently only maven: coordinates and standard Spring Resources (file:, etc...) are supported.
You can also select from the predefined deployables. For example to run Spring Cloud Data Flow execute:
spring cloud dataflow
Config Server git uri
To run configserver with a git repo set the following in ./configserver.yml:
spring:
profiles.active: git
cloud.config.server.git.uri: https://mygitserver/myrepo.git
Stopping
Ctrl-C in the same terminal spring cloud was run.
TODO
- Eureka
- Configserver
- Kafka Broker
- Kafka Bus
- Easy inclusion of default deployables
- H2 Database
- Spring Cloud Dataflow server
- Launcher landing page (Eureka Dashboard works for now)
- Sleuth/Zipkin
- Support external rabbit
- Speedup startup (parallel start?, retry for config server, db and kafka?)
- Cassandra Database
- Client Side Library
- Spring Boot Admin (Not compatible with Brixton)