From 13c264ca755438fb496c636381cf341937bf8d3a Mon Sep 17 00:00:00 2001
From: Deeman <hendriknote@gmail.com>
Date: Sun, 22 Feb 2026 14:01:32 +0100
Subject: [PATCH] fix(deploy): split log dump by service, revert litestream to
 latest
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The 100-line combined log dump was entirely filled by litestream R2
errors, hiding the actual blue-app crash output. Now dumps blue-app
(60 lines), router (10 lines), and litestream (10 lines) separately.

Revert litestream image tag to latest — the R2 errors were caused by
misconfigured endpoint/bucket CI variables, not a litestream version
bug. The v0.5.8 tag may not exist on Docker Hub (tags omit 'v' prefix).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 deploy.sh               | 7 ++++++-
 docker-compose.prod.yml | 2 +-
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/deploy.sh b/deploy.sh
index 492138d..3cce5f8 100755
--- a/deploy.sh
+++ b/deploy.sh
@@ -42,7 +42,12 @@ $COMPOSE --profile "$TARGET" run --rm "${TARGET}-app" \
 echo "==> Starting $TARGET (waiting for health check)..."
 if ! $COMPOSE --profile "$TARGET" up -d --wait; then
     echo "!!! Health check failed — dumping logs"
-    $COMPOSE logs --tail=100 2>&1 || true
+    echo "--- ${TARGET}-app logs ---"
+    $COMPOSE logs --tail=60 "${TARGET}-app" 2>&1 || true
+    echo "--- router logs ---"
+    $COMPOSE logs --tail=10 router 2>&1 || true
+    echo "--- litestream logs ---"
+    $COMPOSE logs --tail=10 litestream 2>&1 || true
     echo "!!! Rolling back"
     $COMPOSE stop "${TARGET}-app" "${TARGET}-worker" "${TARGET}-scheduler"
     LATEST=$($COMPOSE run --rm --entrypoint "" "${TARGET}-app" \
diff --git a/docker-compose.prod.yml b/docker-compose.prod.yml
index 222b4cd..ada76a7 100644
--- a/docker-compose.prod.yml
+++ b/docker-compose.prod.yml
@@ -18,7 +18,7 @@ services:
       start_period: 10s
 
   litestream:
-    image: litestream/litestream:v0.5.8
+    image: litestream/litestream:latest
     restart: unless-stopped
     # Auto-restore from R2 if DB file is missing, then start continuous replication.
     # Handles: new server, deleted volume, disaster recovery.