@@ -30,62 +30,30 @@ developed>> in the ``Getting Started'' section up and running in the Cloud.
30
30
[[cloud-deployment-cloud-foundry]]
31
31
== Cloud Foundry
32
32
Cloud Foundry provides default buildpacks that come into play if no other buildpack is
33
- specified. The Cloud Foundry Java buildpack has excellent support for Spring applications,
34
- including Spring Boot. You can deploy stand-alone executable jar applications, as well as
35
- traditional `.war` packaged applications.
33
+ specified. The Cloud Foundry https://github.com/cloudfoundry/java-buildpack[Java buildpack]
34
+ has excellent support for Spring applications, including Spring Boot. You can deploy
35
+ stand-alone executable jar applications, as well as traditional `.war` packaged
36
+ applications.
36
37
37
38
Once you've built your application (using, for example, `mvn clean package`) and
38
- http://docs.run.pivotal.io /devguide/installcf/install-go-cli.html/ [installed the `cf`
39
- command line tool], simply answer the `cf push` command prompts as follows, substituting
40
- the path to your compiled `.jar` for mine . Be sure to have
41
- http://docs.run.pivotal.io /devguide/installcf/whats-new-v6.html#login[logged in with your
42
- `cf` command line client] before attempting to use it .
39
+ http://docs.cloudfoundry.org /devguide/installcf/install-go-cli.html[installed the `cf`
40
+ command line tool], simply deploy your application using the `cf push` command as follows,
41
+ substituting the path to your compiled `.jar`. Be sure to have
42
+ http://docs.cloudfoundry.org /devguide/installcf/whats-new-v6.html#login[logged in with your
43
+ `cf` command line client] before pushing an application .
43
44
44
45
[indent=0,subs="verbatim,quotes,attributes"]
45
46
----
46
- $ cf push --path target/demo-0.0.1-SNAPSHOT.jar
47
+ $ cf push acloudyspringtime -p target/demo-0.0.1-SNAPSHOT.jar
47
48
----
48
49
49
- If there is a Cloud Foundry `manifest.yml` file present in the same directory, it will be
50
- consulted. If not, the client will prompt you with questions it has about how it should
51
- deploy and manage your application, starting with its name:
50
+ See the http://docs.cloudfoundry.org/devguide/installcf/whats-new-v6.html#push[`cf push`
51
+ documentation] for more options. If there is a Cloud Foundry
52
+ http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html[`manifest.yml`]
53
+ file present in the same directory, it will be consulted.
52
54
53
- [indent=0,subs="verbatim,quotes,attributes"]
54
- ----
55
- Name> *acloudyspringtime*
56
-
57
- Instances> *1*
58
-
59
- 1: 128M
60
- 2: 256M
61
- 3: 512M
62
- 4: 1G
63
- Memory Limit> *256M*
64
-
65
- Creating acloudyspringtime... *OK*
66
-
67
- 1: acloudyspringtime
68
- 2: none
69
- Subdomain> *acloudyspringtime*
70
-
71
- 1: cfapps.io
72
- 2: none
73
- Domain> *cfapps.io*
74
-
75
- Creating route acloudyspringtime.cfapps.io... *OK*
76
- Binding acloudyspringtime.cfapps.io to acloudyspringtime... *OK*
77
-
78
- Create services for application?> *n*
79
-
80
- Bind other services to application?> *n*
81
-
82
- Save configuration?> *y*
83
-
84
- Saving to manifest.yml... *OK*
85
- ----
86
-
87
- NOTE: Here we are substituting `acloudyspringtime` for whatever value you give `cf` when
88
- it asks for the `name` of your application.
55
+ NOTE: Here we are substituting `acloudyspringtime` for whatever value you give `cf`
56
+ as the name of your application.
89
57
90
58
At this point `cf` will start uploading your application:
91
59
@@ -107,7 +75,8 @@ At this point `cf` will start uploading your application:
107
75
0 of 1 instances running (1 starting)
108
76
...
109
77
1 of 1 instances running (1 running)
110
- Push successful! App \'acloudyspringtime' available at acloudyspringtime.cfapps.io
78
+
79
+ App started
111
80
----
112
81
113
82
Congratulations! The application is now live!
@@ -117,11 +86,12 @@ It's easy to then verify the status of the deployed application:
117
86
[indent=0,subs="verbatim,quotes,attributes"]
118
87
----
119
88
$ cf apps
120
- Getting applications in ... OK
89
+ Getting applications in ...
90
+ OK
121
91
122
- name status usage url
92
+ name requested state instances memory disk urls
123
93
...
124
- acloudyspringtime running 1 x 256M acloudyspringtime.cfapps.io
94
+ acloudyspringtime started 1/1 512M 1G acloudyspringtime.cfapps.io
125
95
...
126
96
----
127
97
0 commit comments