vbatts/nodejs-ex
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Added video and tweaked instructions

Browse source
This commit is contained in:
sspeiche 2015-06-04 09:44:39 -04:00
parent 2d036a705c
commit d3b5e4c454
1 changed files with 16 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
README.md
View file

@ -1,4 +1,4 @@
Node.js `echo` Service on OpenShift!
Node.js sample app on OpenShift!
-----------------
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).
@ -11,19 +11,19 @@ One possible option is to use the Docker all-in-one launch as described in the [
If you don't have a project setup all ready, go ahead and take care of that
$ osc new-project nodejs-echo --display-name="nodejs-echo" --description="Sample Node.js app"
$ osc new-project nodejs-echo --display-name="nodejs" --description="Sample Node.js app"
That's it, project has been created. Though it would probably be good to set your current project to this (thought new-project does it automatically as well), such as:
$ osc project nodejs-echo
$ osc project nodejs
### The app ###
Now let's pull in the app source code from [GitHub repo](https://github.com/openshift/nodejs-example) (fork if you like)
Now let's pull in the app source code from [GitHub repo](https://github.com/openshift/nodejs-ex) (fork if you like)
#### create ####
$ osc new-app https://github.com/openshift/nodejs-example
$ osc new-app https://github.com/openshift/nodejs-ex
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.
@ -31,9 +31,9 @@ Note, you can follow along with the web console (located at https://ip-address:8
#### build ####
$ osc start-build nodejs-echo --follow
$ osc start-build nodejs --follow
You can alternatively leave off `--follow` and use `osc build-logs nodejs-echo-n` where n is the number of the build (output of start-build).
You can alternatively leave off `--follow` and use `osc build-logs nodejs-n` where n is the number of the build (output of start-build).
#### deploy ####
@ -52,3 +52,12 @@ Run/test our app by simply doing an HTTP GET request
#### update ####
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.
### Web UI ###
To run this example from the Web UI, you can same steps following done on the CLI as defined above by [The project](#the-project). Here's a video showing it in motion:
<a href="http://www.youtube.com/watch?feature=player_embedded&v=uocucZqg_0I?t=225" target="_blank">
<img src="http://img.youtube.com/vi/uocucZqg_0I/0.jpg"
alt="OpenShift 3: Node.js Sample" width="240" height="180" border="10" /></a>