fleet-manager: run the CI-built image (FLEET_MANAGER_VERSION), keep local build
Point the compose service at the registry image the new CI workflow pushes
(git.bitasylum.org/audiobuzz/fleet-manager:${FLEET_MANAGER_VERSION:-latest}) so
mgmt hosts `docker compose pull` instead of building at deploy time — matching
dnsmasq/spdk/kiosk. `build: .` stays for local dev. Add FLEET_MANAGER_VERSION to
.env.example.
This commit is contained in:
@@ -56,9 +56,13 @@ services:
|
||||
retries: 5
|
||||
|
||||
# --- the control plane + embedded SPA --------------------------------------
|
||||
# CI builds + pushes this image (.gitea/workflows/fleet-manager-image.yaml);
|
||||
# `docker compose pull` fetches it. `build: .` stays so local dev can still
|
||||
# `docker compose build fleet-manager`. Pin FLEET_MANAGER_VERSION in .env to a
|
||||
# CI tag (e.g. main-<sha7>); defaults to :latest.
|
||||
fleet-manager:
|
||||
image: "git.bitasylum.org/audiobuzz/fleet-manager:${FLEET_MANAGER_VERSION:-latest}"
|
||||
build: .
|
||||
image: fleet-manager:local
|
||||
restart: unless-stopped
|
||||
# Host networking: reach the broker on 127.0.0.1:9443 + InfluxDB on
|
||||
# 127.0.0.1:8086, and bind the agent gRPC listener on a routable mgmt addr.
|
||||
|
||||
Reference in New Issue
Block a user