fix(restore): chown wp-content to uid 1000 after docker cp

docker cp copies files owned by root. PHP-FPM in the Minimus image
runs as uid=1000 (wordpress) and cannot write to root-owned directories,
causing plugin/theme updates to fail with 'Could not create directory'.

Fix: after docker cp, exec into the container as root to chown and
chmod the wp-content tree (dirs 755, files 644, owner 1000:1000).
Applied to both remote_restore() and local_restore().

Author: ncimino

wordpress-docker/sites/burnedout-xyz/scripts/restore.sh

@@ -107,6 +107,9 @@ local_restore() {
     WP_CONTAINER="$(docker compose -f compose.local.yaml ps -q wordpress)"
     docker cp "${restore_dir}/wp-content" "${WP_CONTAINER}:/var/www/html/"
   fi
+  # Fix ownership and permissions — docker cp copies as root; PHP-FPM runs as uid 1000
+  docker exec -u root "$WP_CONTAINER" sh -c \
+    "chown -R 1000:1000 /var/www/html/wp-content && find /var/www/html/wp-content -type d -exec chmod 755 {} + && find /var/www/html/wp-content -type f -exec chmod 644 {} +"
   echo "    ✓ wp-content restored"
 
   echo "==> Starting full stack..."
@@ -185,6 +188,9 @@ fi
 
 echo "==> Restoring wp-content..."
 docker cp "${RESTORE_DIR}/wp-content" "${PROJECT_NAME}-wordpress-1:/var/www/html/"
+# Fix ownership and permissions — docker cp copies as root; PHP-FPM runs as uid 1000
+docker exec -u root "${PROJECT_NAME}-wordpress-1" sh -c \
+  "chown -R 1000:1000 /var/www/html/wp-content && find /var/www/html/wp-content -type d -exec chmod 755 {} + && find /var/www/html/wp-content -type f -exec chmod 644 {} +"
 echo "    ✓ wp-content restored"
 
 echo "==> Starting stack..."