From 94d60482e616ff89383ac422e3ac84bd2343fb33 Mon Sep 17 00:00:00 2001
From: Admin <1+admin@noreply.git.dcntrlized.org>
Date: Mon, 19 Oct 2026 14:52:56 +0100
Subject: [PATCH] [build](dev): publish Maestro on all interfaces for a LAN
 phone
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.
---
 docker-compose.debug.yaml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docker-compose.debug.yaml b/docker-compose.debug.yaml
index 2c211b7..780d249 100644
--- a/docker-compose.debug.yaml
+++ b/docker-compose.debug.yaml
@@ -3,8 +3,11 @@ services:
     image: maestro
     container_name: maestro
     ports:
-      # Loopback-only default (dev is localhost anyway); see docker-compose.yaml
-      - "127.0.0.1:8080:8080"
+      # 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"