Task: Package and publish deployer-ui as a production Docker image

[hyde-repo]

Description
Push the latest version of deployer-ui and set up a Docker-based build pipeline that installs the deployer CLI, runs the npm production build, and publishes the resulting image. Deliver a two-stage Dockerfile (builder + runtime/pusher) based on the latest Ubuntu Server LTS, and a docker-compose.yml to build and validate the image locally.

Working branch

• dev

Files / locations

• deployer-ui/Dockerfile - two-stage build (builder → runtime)
• deployer-ui/docker-compose.yml - local build & test orchestration
• deployer-ui/README.md - update with build & push instructions

Requirements

• Base image: latest Ubuntu Server LTS
• Stage 1 (builder): install deployer CLI, run npm ci + npm run build (prod mode)
• Stage 2 (runtime): minimal image serving the built artifacts
• Image must be testable locally via docker compose up
• README updated with clear build & push commands if the current docs are missing or outdated

[t0kubetsu]

A PR addressing this issue has been opened: #43

What was implemented:

• Two-stage Dockerfile using Debian stable (bookworm) as the base — node:24-bookworm-slim for the builder, nginx:stable-bookworm for the runtime. Debian stable was preferred over Ubuntu LTS as it is the reference platform used in our Debian VM test environment and avoids Ubuntu-specific packaging constraints.
• Node.js 24 (latest stable), compatible with the >=22.12.0 engines constraint in package.json.
• range42-deployer CLI installed in the builder stage via an isolated Python venv (/opt/deployer-env) — required on Debian bookworm due to PEP 668 enforcement.
• Optional DEPLOYER_CLI_VERSION build arg to pin the CLI to a specific release.
• docker-compose.yml updated with an explicit healthcheck block.
• README.md extended with a Docker: Build & Push section covering tagging, version pinning, and push commands.