453bb7334f
Previously the manifest for this application was configured such that it used a custom command to start itself (based on Spring Boot). This change removes that custom command and substitutes in the new Java buildpack which takes care of all of the things that command previously did. A byproduct of this is that as improvements are made to the main buildpack they will automatically get included in future pushes of the application. An example of this is that now, if a New Relic service is bound to the application, the application will automatically be configured to use it. [#54518830]
Spring Initializr
Prerequisites
You need Java (1.6 or better) and a bash-like shell.
If you are on a Mac and using homebrew, all you must do to install it is:
$ brew install spring-boot-cli
It will install /usr/local/bin/spring. You can jump right to running the app.
An alternative way to install the spring command line interface can be installed like this:
$ curl spring.cfapps.io/installer | bash
After running that command you should see a spring directory:
$ ./spring/bin/spring --help
usage: spring [--help] [--version]
<command> [<args>]
...
You could add that bin directory to your PATH (the examples below
assume you did that).
If you don't have curl or zip you can probably get them (for
Windoze users we recommend cygwin), or you can
download the zip file and unpack
it yourself.
Running the app
Use the spring command:
$ spring run app.groovy
Deploying to Cloud Foundry
To help avoid a timeout on startup you should upload all the
dependencies. You can get those locally by running the app with
--local:
$ spring run --local app.groovy
this will create a local directory grapes/ with all the jar
dependencies. Then when you cf push they will be uploaded and used
if the app is again launched with --local.