We can see the details of what the S2I builder did. This can be helpful to diagnose issues if builds are failing.
TIP: For a node.js app, running "npm shrinkwrap" is a good practice to perform on your branch before releasing changes that you plan to build/deploy as an image with S2I
Goto the terminal and type the following:
$ oc get builds
Note the name of your build from the above command output and use it to see the logs with:
$ oc logs builds/[BUILD_NAME]
The console will print out the full log for your build. Note, you could pipe this to more or less for easier viewing in the CLI.
Click on "Topology", the "node"/"dc-metro-map" icon, and then on "View logs"
You should see a log output similar to the one below:
Let's see this app in action!
Goto the terminal and type the following (ensure you are in the right project):
$ oc get routes
Copy the HOST/PORT and paste into your favorite web browser:
Click on "Topology"
Click the arrow, at the top right corner of the "dc-metro-map" icon, to launch a new tab/window, with the running app
The app should look like this in your web browser:
Clicking the checkboxes will toggle on/off the individual metro stations on each colored line. A numbered icon indicates there is more than one metro station in that area and they have been consolidated - click the number or zoom in to see more.
In this lab we deployed a sample application using source to image. This process built our code and wrapped that in a docker image. It then deployed the image into our OpenShift platform in a pod and exposed a route to allow outside web traffic to access our application. In the next lab we will look at some details of this app's deployment and make some changes to see how OpenShift can help to automate our development processes. More information about creating new applications can be found here.