Documents the deploy user and test folder rights
Continuous Integration / check (pull_request) Successful in 5m40s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 11m48s
Continuous Integration / deploy-production (pull_request) Skipped

The pipeline logs in as gitea-workflow, a member of the www-data group.
The test folder needs group write access (775, or 2775 with setgid);
new folders get 755 by default, which made the first deploys fail.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 09:41:36 +02:00
co-authored by Claude Opus 5.5
parent 736756a36b
commit 7750971170
2 changed files with 23 additions and 3 deletions
@@ -774,3 +774,15 @@ Verder heb ik de vraag ook beantwoord"
**Context**: OPERATIONS - Deployment Setup
---
## Deployment Setup - Deploy User and Folder Rights in Instructions
**Timestamp**: 2026-10-19T07:41:36Z
**User Input**: "kan in de deployinstructies worden opgenomen dat voor de pipeline de gebruiker gitea-workflow gebruikt moet worden. die zit in de www-data groep en die groep moet wel schrijfrechten hebben. ik had bijvoorbeeld met de webadmin gebruiker in filezilla de map aangemaakt. die zit ook in de www-data groep, maar de rechten worden standaard 755 en die staan nu op 775 en dat werkte dus."
**AI Response**: "Updated deployment-instructions.md: PI_MAIN_USERNAME = gitea-workflow (member of www-data); step 1.2.1 now creates the folder with chgrp www-data and chmod 2775, explains the 755 default (FileZilla/mkdir) pitfall, setgid tip, and the external-disk symlink; added a troubleshooting row for mkdir/scp Permission denied. Pushing to the PR #4 branch (restarts the PR run)."
**Context**: OPERATIONS - Deployment Setup
---