This getting started experience walks you through the “long way” of getting the same sample project from the Basic Walkthrough topic up and running on Digital Garage. The following sections guide you through creating a project that contains a sample Node.js application that will serve a welcome page and the current hit count (stored in a database). This involves creating two pods:

  • one to host the Node.js application

  • one to host the MongoDB database

The tutorial assumes that you have:

  • a Digital Garage account.

  • a GitHub account.

  • Git installed locally.


In this section, you will fork the Digital Garage Node.js sample application on GitHub and clone the repository to your local machine so that you can deploy and edit the application.

You can skip this step if you already forked the thedigitalgarage/nodejs-ex repository when following the Basic Walkthrough topic.

  1. On GitHub, navigate to the thedigitalgarage/nodejs-ex repository. In the top-right corner of the page, click Fork:

    Fork the project
  2. Next, execute the following commands on your local machine to clone the sample application and change to the new directory:

    $ git clone https://github.com/<your_github_username>/nodejs-ex
    $ cd nodejs-ex

That’s it! Now, you have a fork of the original thedigitalgarage/nodejs-ex example application Git repository and a copy on your local machine.

Installing the Digital Garage CLI

In this section, you will install the Digital Garage CLI. The Digital Garage CLI exposes commands for managing your applications, as well as lower level tools to interact with each component of your system.

  1. First, download the Digital Garage CLI from the Command Line Tools page in the Digital Garage web console. You find the Command Line Tools menu item under the Support button (?) on the left side of the top menu bar. The CLI is available for Linux (32- or 64-bit), Mac OS X, and Windows. After you have downloaded the CLI, return to these steps.

  2. Next, unpack or unzip the archive and move the oc binary to a directory on your PATH.

    To check your PATH on Linux or Mac OS X, open the Terminal and run:

    $ echo $PATH

    To check it on Windows, open the Command Prompt and run:

    C:\> path

    After it is installed, you can use the oc command from your command shell.

  3. Then, visit the Command Line Tools page in the Digital Garage web console and copy the oc login command shown with your current session token to log in to Digital Garage from the CLI:

    $ oc login https://apps.thedigitalgarage.io:8443 --token=<your_session_token>

    The oc login command is the best way to initially set up the Digital Garage CLI. The information is automatically saved in a CLI configuration file that is then used for subsequent commands.

Creating a New Application from Source Code

In this section, you will deploy your first application to Digital Garage using the web console.

  1. First, if you have multiple projects, verify that you are in the correct project. Replace <project_name> below with a unique name for your project, such as <your_github_username>-example:

    $ oc project <project_name>

    If you followed the Basic Walkthrough topic, you already created your first project. You must switch to your project namespace and clear out the original sample application.

  1. Use the following command to find the name of your existing project(s):

    $ oc get projects
  2. Next, switch to your project namespace:

    $ oc project <your_project_name>
  3. Then, delete all existing objects in your project:

    $ oc delete all --all
  4. Use the following command to find the name of your existing persistent volume claims:

    $ oc get pvc
  5. Finally, delete your existing persistent volume claims with:

    $ oc delete pvc mongodb
    1. Next, create a new application from your forked copy of the nodejs-ex source code file:

      $ oc new-app https://github.com/<your_github_username>/nodejs-ex --name nodejs-mongodb-example

The --name option will apply a name of nodejs-mongodb-example to all the resources created by the oc new-app command, for easy management later.

+ The tool will inspect the source code, locate an appropriate image that can build the source code, create an image stream for the new application image that will be built, then create the correct build configuration, deployment configuration and service definition.

+ The oc new-app command kicks off a build after all required dependencies are confirmed and automatically deploys the application after the image is available.

You can follow along on the Overview page for your project in the web console to see the new resource being created and watch the progress of the build and deployment. When the Node.js pod is running, the build is complete.

You can also use the oc status command to check the status of your new nodejs app, as well as oc get pods to check when the pod is up and running.

The oc get services command tells you what IP address the service is running; the default port it deploys to is 8080.

== Configuring Routes

In this section, you will configure a route to expose your Node.js service to external requests.

  1. First, find your service name (which should be nodejs-mongodb-example with:

    $ oc get services
  2. Next, create a route to expose your service to external requests:

    $ oc expose service/nodejs-mongodb-example
  3. Now you can find the external host/port for your service with:

    $ oc get routes
  4. Finally, copy the route HOST/PORT for your application and paste it in the browser to view your application: