Wedeploy-console NPM

console

WeDeploy Console helps you deploy, scale and analyze production issues in a simple web based interface

Image

The wedeploy/console:beta image can be built by running the ./build-image.sh script. With it you can customize some parameters of the build:

variable	description
`IMAGE_PREFIX`	Configures the prefix of the image (defaults to `wedeploy`)
`IMAGE_TAG`	Configures the tag of the image (defaults to `beta`)

For instance:

IMAGE_PREFIX=localhost:5000/cirocosta.co \
  IMAGE_TAG=dev \
  ./build-image.sh


# Starting to build image

#   FULL_NAME:              localhost:5000/cirocosta.co/console:dev
#   IMAGE_PREFIX:           localhost:5000/cirocosta.co
#   IMAGE_TAG:              dev
#   CONTEXT:                /Users/cirocosta/Development/wedeploy/console

Note.: the Dockerfile makes use of the local node_modules directory in order to improve image building performance. If no node_modules is present, then the image building will take care of running npm i, fetching all the dependencies. However, if you have non-fresh dependencies locally, it'll use them in the build.

Note 2.: The image relies on the WeDeploy infrastructure running in order to function well as it self-registers in a consul server at wedeploy-consul-server:8500 and sends its health status to it periodically. Thus, you can either test it locally by running ./run-infra.sh from wedeploy/images (after making sure you have the latest images locally - check wedeploy/images/README.md).

To push the image execute ./push-image.sh. It accepts the same environment variables as ./build-image. Note that in order to push to wedeploy/* you have to have logged in first (and have the right set of permissions). You can do so with docker login.