Lets the test deploy work with group write access

`scp -r dist/.` also sets the mode of the target folder, which only its
owner may do. Copying the contents (`dist/*`, with dotglob for hidden
files) leaves the folder itself alone, so group write access on the test
folder is enough.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 09:32:23 +02:00
co-authored by Claude Opus 5.5
parent a87602ef5a
commit 67ef16b9f2
2 changed files with 30 additions and 1 deletions
+6 -1
View File
@@ -196,7 +196,12 @@ jobs:
fi
mkdir -p '$DEPLOY_PATH'
find '$DEPLOY_PATH' -mindepth 1 -delete"
sshpass -e scp -P "$SSH_PORT" -o StrictHostKeyChecking=accept-new -r dist/. "$SSH_USER@$SSH_HOST:$DEPLOY_PATH/"
# De inhoud kopiëren (dist/*), niet de map zelf (dist/.): dan probeert
# scp de rechten van de doelmap niet te zetten, wat alleen de eigenaar
# mag. Zo zijn groeps-schrijfrechten op de doelmap genoeg.
# dotglob: ook bestanden die met een punt beginnen gaan mee.
shopt -s dotglob
sshpass -e scp -P "$SSH_PORT" -o StrictHostKeyChecking=accept-new -r dist/* "$SSH_USER@$SSH_HOST:$DEPLOY_PATH/"
echo "Gedeployd naar test: ${GITHUB_REF_NAME} (${GITHUB_SHA::7})"
- name: Controle na deploy
@@ -738,3 +738,27 @@ Verder heb ik de vraag ook beantwoord"
**Context**: OPERATIONS - Deployment Setup
---
## Deployment Setup - Run 531 Re-run Result
**Timestamp**: 2026-10-19T07:08:01Z
**User Input**: "ik zie niet dat je de run in de gaten aan het houden bent, klopt dat? Hij zit al in de deploy-test en heb je nog niks zien zeggen over de run"
**AI Response**: "Explained the watcher only notified at run completion. Re-run of 531: check and lighthouse succeeded; deploy-test resolved the symlink (/var/www/html/andreaslop-test -> /mnt/storage1/www/html/andreaslop-test), SSH login, WordPress guard and mkdir OK; scp failed with 'Permission denied' on files and 'remote setstat' on the folder: deploy user lacks write access and is not the owner. Asked owner to chown the target folder to the SSH user and re-run the failed job. Watcher extended with STOP_ON_JOB to report as soon as deploy-test finishes; started for the next re-run."
**Context**: OPERATIONS - Deployment Setup; awaiting owner action on the Pi
---
## Deployment Setup - Test Folder Permissions
**Timestamp**: 2026-10-19T07:32:23Z
**User Input**: "hoe doet de workspace `K:\Development\Projects\SimpleDeckApp` het in de deployment? want die kan wel deployen terwijl daar dezelfde rechten op staan en dezelfde gebruiker wordt gebruikt" / "ik heb de rechten aangepast. de gebruiker zat al wel in de juiste groep, maar ik zag dat die nog niet mocht schrijven naar de map. alleen uitlezen en uitvoeren. dus even deze run afwachten nu"
**AI Response**: "SimpleDeckApp creates a new releases/<timestamp> folder as the SSH user before scp, so the user owns its target; our pipeline wrote into an existing folder not owned by the user. Owner gave the group write access. Remaining issue: scp -r dist/. also sets the target folder's mode (setstat), which only the owner may do. Changed deploy-test to copy dist/* with dotglob (contents, not the folder; hidden files included, verified locally), so group write is sufficient. Pushed to feature/frontend-shell; current run 531 still uses the old step."
**Context**: OPERATIONS - Deployment Setup; watching run 531
---