tackle2-hub

Tackle (2nd generation) hub component.

See settings for configuration.

The hub provides a REST API, inventory and task manager.

Development

Prerequisites

• Go (see go.mod for the required version)
• Node.js >= 22 and npm >= 10 (required only when working on the login page)

Building

Build the hub binary and the login page frontend in one step:

make hub

Running locally with the login page

The hub reads login page assets from LOGIN_PAGE_PATH (default /opt/app/login-page). The run target builds the frontend, then runs the hub binary with LOGIN_PAGE_PATH automatically pointed at the local build output (login-page/dist):

make run

To override the path (e.g. a pre-built copy elsewhere):

make run LOGIN_PAGE_PATH=/path/to/login-page/dist

Building the login page separately

make login-page

This runs npm ci (only when node_modules/ is absent or package-lock.json changes) followed by npm run build. Output goes to login-page/dist/.

To clean login page build artifacts:

make clean-login-page

Container builds

The container build handles the login page through a dedicated builder stage in the Dockerfile and does not require a local Node.js installation:

make podman-build   # or make docker-build

Code of Conduct

Refer to Konveyor's Code of Conduct here.