Skip to content

Commit a4f2d94

Browse files
committed
Merge pull request #20 from bparees/cleanup
polish the readme some more
2 parents c263083 + 605ce4e commit a4f2d94

File tree

1 file changed

+13
-9
lines changed

1 file changed

+13
-9
lines changed

README.md

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
Node.js sample app on OpenShift!
22
-----------------
33

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).
55

66
### OpenShift setup ###
77

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).
99

1010
### The project ###
1111

@@ -23,9 +23,9 @@ Now let's pull in the app source code from [GitHub repo](https://github.com/open
2323

2424
#### create ####
2525

26-
$ oc new-app https://github.com/openshift/nodejs-ex
26+
$ oc new-app https://github.com/openshift/nodejs-ex -l name=myapp
2727
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.
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.
2929

3030
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.
3131

@@ -45,19 +45,23 @@ This will help indicate what IP address the service is running, the default port
4545

4646
#### enjoy ####
4747

48-
Run/test our app by simply doing an HTTP GET request
48+
Determine the service ip for the application by running
4949

50-
$ curl ip-address:8080
50+
$ oc svc
51+
52+
Run/test your app by browsing to
53+
54+
$ curl service-ip-address:8080
5155

5256
#### update ####
5357

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.
5559

5660
#### delete ####
5761

58-
$ oc delete all --all
62+
$ oc delete all -l name=myapp
5963

60-
To remove all the resources created for you application.
64+
To remove all the resources with the label "name=myapp".
6165

6266
### Web UI ###
6367

0 commit comments

Comments
 (0)