Files
Maestro/docker-compose.debug.yaml
T
Admin 94d60482e6 [build](dev): publish Maestro on all interfaces for a LAN phone
The debug stack is the instance an app on the phone talks to, and Maestro is the
only port an app is ever given (the single data plane routes every service under
/api/{service}). Binding 127.0.0.1 makes the instance unreachable from a device
on the LAN — only USB with `adb reverse` could reach it — so the dev compose now
publishes on 0.0.0.0.
2026-10-19 14:52:56 +01:00

37 lines
1.4 KiB
YAML

services:
maestro-engine:
image: maestro
container_name: maestro
ports:
# All interfaces: the debug stack is the instance a phone on the LAN
# talks to, and Maestro is the only port an app is ever given (the single
# data plane). Loopback-only makes the instance invisible to a device that
# is not using `adb reverse`. See docker-compose.yaml for the prod bind.
- "0.0.0.0:8080:8080"
volumes:
- "/var/run/docker.sock:/var/run/docker.sock"
- "${XDG_DATA_HOME:-${HOME}}/.dcntrlized:/data/.dcntrlized"
- "${HOME}:/host-home:ro"
networks:
- dcntrlized_net
build:
context: .
dockerfile: Dockerfile.debug
environment:
- DCNTRLIZED_DEV=true
- XDG_DATA_HOME=/data
# Host path backing the data root, so Maestro's containerized start path
# can produce bind-mount sources the daemon resolves on the host
# namespace (identity injection for infra/peers).
- DCNTRLIZED_HOST_DATA_ROOT=${XDG_DATA_HOME:-${HOME}}/.dcntrlized
- DCNTRLIZED_GITEA_URL=${DCNTRLIZED_GITEA_URL:-http://192.168.122.183:3000}
- GITEA_REGISTRY_RO_TOKEN=${GITEA_REGISTRY_RO_TOKEN}
- GITEA_RW_PACKAGE_TOKEN=${GITEA_RW_PACKAGE_TOKEN}
- GITEA_ORG=${GITEA_ORG:-Dcntrlized}
- GITEA_USER=${GITEA_USER:-admin}
- GIT_TOKEN=${GIT_TOKEN}
- REGISTRY_USER=${REGISTRY_USER:-admin}
networks:
dcntrlized_net:
external: true