Files
spring-cloud-cli/docs
Marcin Grzejszczak 533be6dedf Deploying documentation to proper folder
What we're missing ATM is different documentation versions for different application versions. What this change does is that it's:

- finding out what is the current branch (e.g. 1.0.x)
- finding out out what is the name of the main adoc file (e.g. spring-cloud-sleuth)
- pulling the changes from gh-pages after checkout
- finding out what is the list of comma separated whitelisted branches (via the `docs.whitelisted.branches` prop)
- in gh-pages creating a folder with name of the branch  (e.g. /1.0.x)
copying all the docs/target/generated-docs/ to that folder
- if the branch from which we're calling the script is NOT master then we're changing the ${main.adoc}.html to index.html so that it's easier to access the docs (e.g. http://cloud.spring.io/spring-cloud-sleuth/1.0.x/)
2016-08-16 15:41:50 +02:00
..
2016-03-24 11:27:20 +00:00

// Do not edit this file (e.g. go instead to src/main/asciidoc)

Spring Boot command line features for
https://github.com/spring-cloud[Spring Cloud].


== Installation

To install, make
sure you have
https://github.com/spring-projects/spring-boot[Spring Boot CLI]
(1.1.x with x>=5):

    $ spring version
    Spring CLI v1.3.3.RELEASE

E.g. for GVM users

```
$ gvm install springboot 1.3.3.RELEASE
$ gvm use springboot 1.3.3.RELEASE
```

then get the install command plugin (backported from Boot 1.2.0):

```
$ wget http://dl.bintray.com/dsyer/generic/install-0.0.1.jar
```

install it in the Spring Boot CLI, e.g. with GVM (MacOS users that rely on brew might have to find the `/lib` directory by scanning `brew info springboot`):

```
$ cp install-0.0.1.jar ~/.gvm/springboot/1.3.3.RELEASE/lib
```

and finally install the Spring Cloud plugin:

```
$ mvn install
$ spring install org.springframework.cloud:spring-cloud-cli:1.1.0.RC1
```