Skip to content

Latest commit

 

History

History
executable file
·
139 lines (99 loc) · 4.51 KB

README.md

File metadata and controls

executable file
·
139 lines (99 loc) · 4.51 KB
Raw

Example Application for Source-to-Image Node.js & NGINX Builds

An example static web application that contains scripts to simplify deployment on OpenShift as an NGINX container.

This application uses the following libraries/tools, but you can replace them with your preferred stack:

  • React
  • Tailwind CSS
  • TypeScript
  • Webpack
  • npm

Build & Run Locally

First install dependencies:

# install dependencies
npm install

# run in hot module reloading mode
npm start

Create a Production Bundle

This will generate a bundle of production optimised static assets in a dist/ directory in the project folder:

npm run build

Create a Development Bundle

This will generate a bundle of static assets in a dist/ directory in the project folder:

npm run build:dev

Create a Deployable NGINX Container Image

Each of the options below relies on the npm build (alias for npm run build) command to create a dist/ folder in the root of your project that contains all the static assets for the application, i.e HTML, CSS, JavaScript, and binary files.

This folder can safely (and probably shouldbe !) added to the gitignore since each build option will generate it using npm build.

Using Chained s2i Builds on OpenShift

Uses source-to-image (s2i) on an OpenShift cluster to chain two builds. Requires the OpenShift CLI.

The first build uses a Node.js builder image to prepare the static assets using Webpack. The second build uses an NGINX builder image to take the static assets from the first Node.js build and produce a deployable NGINX container image.

export GIT_REPO=https://github.com/evanshortiss/s2i-nodejs-nginx-example

# Create a Node.js build to run Webpack and store the results
# in a Node.js container image. This image won't be deployed
oc new-build nodejs~$GIT_REPO --name webapp-npm-build

# After the first build is finished and stored in
# the OpenShift registry pass it to an NGINX build
oc new-build --name=webapp-nginx-runtime \
--docker-image=centos/nginx-116-centos7 \
--source-image=webapp-npm-build \
--source-image-path="/opt/app-root/src/dist/.:." \
--strategy=source

# Create a Deployment the new nginx container
oc new-app webapp-nginx-runtime

# Optional label/annotations to show an NGINX
# icon on the topology view in the OpenShift UI
oc annotate dc/webapp-nginx-runtime app.openshift.io/runtime=nginx
oc label dc/webapp-nginx-runtime app.openshift.io/runtime=nginx

The second build (webapp-nginx-runtime) will start anytime the first build (webapp-npm-build) finishes. Run oc start-build webapp-nginx-runtime to trigger a new build, or setup your own Build Triggers.

Using a Custom s2i Build Image on OpenShift

Uses source-to-image (s2i) to perform a single build. Requires the OpenShift CLI.

export GIT_REPO=https://github.com/evanshortiss/s2i-nodejs-nginx-example
export BUILDER_IMAGE=quay.io/evanshortiss/s2i-nodejs-nginx

# Build and deploy the application using the s2i-nodejs-nginx builder
oc new-app $BUILDER_IMAGE~$GIT_REPO --name webapp-npm-build

Using a Local s2i Build

Uses source-to-image (s2i) to create an NGINX container image that serves the application assets.

You need to install s2i and Docker before running the commands below to generate a container image.

Once s2i is installed, create a build with the following command:

# use the s2i-nodejs-nginx image with Node.js 14 to build this application
# into a deployable NGINX 1.18 container image named "my-web-app"
s2i build -c . quay.io/evanshortiss/s2i-nodejs-nginx:14-nginx1.18 my-web-app

Alternatively use this shorthand command:

npm run docker:build

And run it locally using Docker or Podman:

docker run -p 8080:8080 my-web-app

Credits

  • Initial project structure was generated using createapp.dev
  • Star Wars icons created by Symbolicons. The icon set can be found here.