Dcntrlized/Maestro
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[build](dev): publish Maestro on all interfaces for a LAN phone

Browse Source 
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.
This commit is contained in:
Admin
2026-10-19 14:52:56 +01:00
parent ef4c7c584d
commit 94d60482e6
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-compose.debug.yaml
+5 -2
View File
@@ -3,8 +3,11 @@ services:
image: maestro image: maestro
container_name: maestro container_name: maestro
ports: ports:
# Loopback-only default (dev is localhost anyway); see docker-compose.yaml # All interfaces: the debug stack is the instance a phone on the LAN
- "127.0.0.1:8080:8080" # 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: volumes:
- "/var/run/docker.sock:/var/run/docker.sock" - "/var/run/docker.sock:/var/run/docker.sock"
- "${XDG_DATA_HOME:-${HOME}}/.dcntrlized:/data/.dcntrlized" - "${XDG_DATA_HOME:-${HOME}}/.dcntrlized:/data/.dcntrlized"