Getting Started

This page describes how to configure applications so they are recognized and correctly connected to ICC.

Prerequisites

• ICC installed correctly and running
• A npm user authorized by Platformatic and a valid authToken for it.

ICC - Initial State

When ICC is deployed and started the first time, no applications are shown

Application setup

To have an application to show up in ICC, the application must include among its dependencies @platformatic/wattpro and the app environment must include the PLT_ICC_URL variable specifying the ICC URL

Caution

It’s also possible to specify the application name with PLT_APP_NAME, but if not set, ICC will get the application name from K8s automatically.

An example of Dockerfile is:

FROM node:22-alpine

ENV APP_HOME=/home/app/node/

RUN mkdir -p $APP_HOME/node_modules && chown -R node:node $APP_HOME

## This is necessary to access private `npm` repositories
RUN --mount=type=secret,id=npmrc cp /run/secrets/npmrc /root/.npmrc

## This is the actual platformatic runtime that executes your node app
RUN npm install -g "@platformatic/wattpro@latest"

WORKDIR $APP_HOME

COPY ./ ./

USER node

EXPOSE 3042
EXPOSE 7777

CMD [ "wattpro", "start" ]

Note that this Dockerfile assumes that a secret named npmrc is passed. Check the Docker configuration about it, but one way is with --secret=id=npmrc,src=~/.npmrc.

The .npmrc must contain the npm authToken authorized to access the @platformatic/wattpro npm package and provided by Platformatic.

Note

This is only one of the options that can be used to add @platformatic/wattpro. Another (simpler) one is to just add it directly as project dependency in the package.json.

Once the application is deployed and started on K8s, it will appear on ICC:

Open the application detail to see the application and K8s metrics: