You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
Node.js sample app on OpenShift!
2
2
-----------------
3
3
4
-
This example will serve an http response of various "machine" stats from the "machine" the Node.js app is running on to [http://host:8080](http://host:8080).
4
+
This example will serve a welcome page and the current hit count as stored in a database to [http://host:8080](http://host:8080).
5
5
6
6
### OpenShift setup ###
7
7
8
-
One possible option is to use the Docker all-in-one launch as described in the [origins project](https://github.com/openshift/origins).
8
+
One option is to use the Docker all-in-one launch as described in the [origins project](https://github.com/openshift/origins).
9
9
10
10
### The project ###
11
11
@@ -23,9 +23,9 @@ Now let's pull in the app source code from [GitHub repo](https://github.com/open
That should be it, `new-app` will take care of creating the right build configuration, deployment configuration and service definition. Next you'll be able to kick off the build.
28
+
That should be it, `new-app` will take care of creating the right build configuration, deployment configuration and service definition. Next you'll be able to kick off the build. The -l flag will apply a label of "name=myapp" to all the resources created by new-app, for easy management later.
29
29
30
30
Note, you can follow along with the web console (located at https://ip-address:8443/console) to see what new resources have been created and watch the progress of the build and deployment.
31
31
@@ -45,19 +45,23 @@ This will help indicate what IP address the service is running, the default port
45
45
46
46
#### enjoy ####
47
47
48
-
Run/test our app by simply doing an HTTP GET request
48
+
Determine the service ip for the application by running
49
49
50
-
$ curl ip-address:8080
50
+
$ oc svc
51
+
52
+
Run/test your app by browsing to
53
+
54
+
$ curl service-ip-address:8080
51
55
52
56
#### update ####
53
57
54
-
Assuming you used the URL of your own forked report, we can easily push changes to that hosted repo and simply repeat the steps above to build (this is obviously just demonstrating the manually kicking off of builds) which will trigger the new built image to be deployed.
58
+
Assuming you used the URL of your own forked report, we can easily push changes to that hosted repo and simply repeat the steps above to build which will trigger the new built image to be deployed.
55
59
56
60
#### delete ####
57
61
58
-
$ oc delete all --all
62
+
$ oc delete all -l name=myapp
59
63
60
-
To remove all the resources created for you application.
64
+
To remove all the resources with the label "name=myapp".
0 commit comments