From 2cd2f9c443b8fd02e99392bcfd60a6db87568b3a Mon Sep 17 00:00:00 2001 From: dlynas <118506937+dlynas@users.noreply.github.com> Date: Tue, 5 May 2026 00:46:45 -0400 Subject: [PATCH] fix: skip recursive chown on startup when UIDs are already correct The unconditional chown -R on every container start was walking the entire /app tree (including large music libraries) even when nothing needed fixing. Now only the directory nodes themselves are chowned at startup; the recursive walk still runs inside the UID-change branch where it is actually needed. Co-Authored-By: Claude Sonnet 4.6 --- entrypoint.sh | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/entrypoint.sh b/entrypoint.sh index 1c9f1382..49c99f9c 100644 --- a/entrypoint.sh +++ b/entrypoint.sh @@ -63,9 +63,11 @@ echo " 📄 Updating settings.py to current version..." cp /defaults/settings.py /app/config/settings.py chown soulsync:soulsync /app/config/settings.py 2>/dev/null || true -# Ensure all directories exist and have proper permissions +# Ensure all directories exist with correct ownership. +# Only the directory nodes themselves need chown here — the recursive chown +# above already ran if UIDs changed, so avoid walking the whole tree every start. mkdir -p /app/config /app/data /app/logs /app/downloads /app/Transfer /app/Staging -chown -R soulsync:soulsync /app/config /app/data /app/logs /app/downloads /app/Transfer /app/Staging 2>/dev/null || true +chown soulsync:soulsync /app/config /app/data /app/logs /app/downloads /app/Transfer /app/Staging 2>/dev/null || true echo "✅ Configuration initialized successfully"