- 05 Mar, 2018 1 commit
-
-
Tetsushi Awano authored
This commit enables client and server to work out of the box on CloudFoundry. The client derives the registration info (url and metadata) from the VCAP environment variables. The server computes a unique instanceId and the correct headers for the cf router based on the metadata provided by instances. Also suppots the CloudFoundry discovery client ootb. closes #434
-
- 12 Jan, 2018 1 commit
-
-
Josh Long authored
This removes the spring-boot-starter-parent from the build, and duplicates the necessary plugin configuration in he Spring Boot Admin' parent instead. This way our BOM doesn't include version for dependencies managed by boot's BOM
-
- 15 Nov, 2016 1 commit
-
-
Johannes Edmeier authored
With this commits the server no longer depends on the client. The classes for the clients are moved to de.codecentric.boot.admin.client package. Since the perspective on applications is totally different from client and server the model has been split apart. What means this for users: 1) The client is no longer a transitive dependency for your admin server you may need to add it explicitly to your dependencies, respectively jolokia-core in case you're using discovery and want to use the jmx-bean interface 2)In case you have cutomised parts of the client you need to reflect the package change. fixes #332
-
- 07 Mar, 2015 1 commit
-
- 22 Sep, 2014 1 commit
-
-
Dennis Schulte authored
-