SLP_Software/slp-modular-cms
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

Fixes the account model deploy setup got wrong

Browse Source 
webadmin turned out to be FTP-only and belongs to whoever uploads
customer websites, not to this pipeline. Switched to a separate
deploy account with its own home-directory paths, well away from
where the other sites live, and made the persistent website symlink
cross into webadmin's territory instead of the other way around.
This commit is contained in:
Sluijsens
2026-07-28 19:41:34 +02:00
parent cf80f827ae
commit 2f243f23c3
5 changed files with 157 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidlc-docs/features/gitea-deployment-workflow/audit.md
+22
View File
@@ -1257,3 +1257,25 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: OPERATIONS — Deployment Setup complete, presenting completion message
---
## Deployment Setup — Real Host Facts Surface a Gap (Clarification Needed)
**Timestamp**: 2026-07-28T03:40:00Z
**User Input**: "Ik weet niet wat er als locatie werd gekozen voor alle bestanden en applicaties, maar het pad op de pi waar alle websites in komen is /mnt/storage1/www/html/. De gebruiker webadmin kan niet via ssh inloggen. Dus als we die willen gebruiken moet er wat veranderd worden. Bij filezilla logt webadmin in op locatie /mnt/storage1/www/ wat daar de root / is."
**AI Response**: "This surfaces a real gap: deploy-scp.yaml needs SSH shell access (mkdir, ln -sfn, systemctl --user restart, the backup script), not just SFTP file transfer, which is what webadmin apparently has via FileZilla. Rather than guess which account to use or assume webadmin's role, created deployment-clarification-questions.md asking: (1) which account the deploy pipeline should use — grant webadmin shell access, reuse the reference project's existing SSH-capable account, or create a new one; (2) the real directory placement under /mnt/storage1/www/html/; (3) whether webadmin is actually meant for the WEBSITE_WORKSPACE.md website-author role rather than the CMS's own deploy pipeline."
**Context**: OPERATIONS — Deployment Setup, real host facts revealed an access-model gap; awaiting clarification before correcting deployment-instructions.md
---
## Deployment Setup — Revised for Real Host Facts
**Timestamp**: 2026-07-28T03:50:00Z
**User Input**: "Ik heb de vragen ingevuld, ga verder" (Q1=C preferred/A fallback, Q2=X — deploy path should live in Gitea variables and can be a separate path next to html/, Q3=X — webadmin for website uploads, separate account for the pipeline)
**AI Response**: "Revised deployment-instructions.md and deployment-plan.md: webadmin stays FileZilla/SFTP-only for website-workspace authors; a new dedicated SSH-capable account runs the deploy pipeline instead (with a documented fallback to granting webadmin shell access only if a new account isn't feasible). Deploy paths moved to that account's own home directory, away from /mnt/storage1/www/html/, confirming the existing DEPLOY_PATH_* Gitea variables already make this configurable without a workflow change. shared/wwwroot-web is now documented as a cross-account symlink to wherever webadmin uploads the customer's site, with a one-time shared-group permission setup noted as a host-setup requirement. Renumbered affected sections (1.1-1.9) and fixed all internal cross-references."
**Context**: OPERATIONS — Deployment Setup artifacts corrected before final approval
---