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

Labels every command with who runs it and where

Browse Source 
Four contexts got tangled together across the doc as it grew: pi-main
as root, pi-main as gitea-workflow, the separate proxy Pi, and Gitea's
own web UI. Added a legend up front and tagged every single command
block so it's no longer something the reader has to infer.
This commit is contained in:
Sluijsens
2026-07-29 14:14:58 +02:00
parent c438ec8b1d
commit 459c347c12
2 changed files with 65 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidlc-docs/features/gitea-deployment-workflow/audit.md
+10
View File
@@ -1409,3 +1409,13 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: OPERATIONS — Deployment Setup, real host config revealed the reference project's nginx Sentry-tunnel pattern was carried over unnecessarily and conflicts with this app's own built-in tunnel
---
## Deployment Setup — Explicit Who/Where Labels on Every Command
**Timestamp**: 2026-07-29T01:00:00Z
**User Input**: "in de deployment instructions i snou niet echt duidelijk wanneer je als welke gebruiker de commando's moet draaien"
**AI Response**: "Added a legend near the top of deployment-instructions.md defining four contexts (pi-main/root, pi-main/gitea-workflow, proxy Pi/root, Gitea web UI) and labelled every single command block throughout the document with one of them — account creation, lingering, directory setup, shared/env, systemd units, the entire nginx/certbot section (now clearly proxy-Pi-only except the pi-main firewall step), backup credentials, the backup script itself and its manual verification, and the Gitea Actions variables (explicitly called out as not a host command at all)."
**Context**: OPERATIONS — Deployment Setup, clarity pass across the whole instructions document
---