fix(setup): poll /api/status (not /api/health) in the kiosk wait-loop

The server exposes /api/status, not /api/health — so the all-in-one kiosk
"wait for server" loop never succeeded and burned the full timeout (~120s)
before launching Chromium on every boot. Fixed in the new Debian script and
the Raspberry Pi script it was based on.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
ScreenTinker 2026-06-23 23:46:02 -05:00
parent 7256fd0353
commit d57d5ef591
2 changed files with 2 additions and 2 deletions

View file

@ -297,7 +297,7 @@ fi
if echo "\$KIOSK_URL" | grep -q "localhost"; then
echo "Waiting for ScreenTinker server..."
for i in \$(seq 1 60); do
if curl -sf "http://localhost:${SCREENTINKER_PORT}/api/health" >/dev/null 2>&1; then
if curl -sf "http://localhost:${SCREENTINKER_PORT}/api/status" >/dev/null 2>&1; then
echo "Server ready after \${i}x2s"
break
fi

View file

@ -280,7 +280,7 @@ fi
if echo "\$KIOSK_URL" | grep -q "localhost"; then
echo "Waiting for ScreenTinker server..."
for i in \$(seq 1 30); do
if curl -sf "http://localhost:${SCREENTINKER_PORT}/api/health" >/dev/null 2>&1; then
if curl -sf "http://localhost:${SCREENTINKER_PORT}/api/status" >/dev/null 2>&1; then
echo "Server ready"
break
fi