From 366e912e73796d062886361fa161ac02ad41dfb4 Mon Sep 17 00:00:00 2001 From: Sluijsens Date: Tue, 28 Jul 2026 19:51:10 +0200 Subject: [PATCH] Renames the example deploy account to gitea-workflow pi-deploy restated the obvious (it's on the Pi) without saying what the account is actually for. --- .../features/gitea-deployment-workflow/audit.md | 11 +++++++++++ .../operations/deployment/deployment-instructions.md | 6 +++--- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/aidlc-docs/features/gitea-deployment-workflow/audit.md b/aidlc-docs/features/gitea-deployment-workflow/audit.md index ef7ae7c..ea40161 100644 --- a/aidlc-docs/features/gitea-deployment-workflow/audit.md +++ b/aidlc-docs/features/gitea-deployment-workflow/audit.md @@ -1290,3 +1290,14 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an **Context**: OPERATIONS — Deployment Setup, small correction before final approval --- +## Deployment Setup — Account Name Renamed + +**Timestamp**: 2026-07-28T04:05:00Z + +**User Input**: "kan je hem anders \"gitea-workflow\" noemen? pi-deploy is het namelijk ook niet helemaal. Het is logisch dat het een pi account is want het is op de pi." + +**AI Response**: "Renamed the example deploy account from pi-deploy to gitea-workflow throughout deployment-instructions.md — better reflects that it's the account the Gitea Actions workflow uses specifically, rather than restating the redundant fact that it's on the Pi." + +**Context**: OPERATIONS — Deployment Setup, naming correction before final approval + +--- diff --git a/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md b/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md index e258455..0a8d0e8 100644 --- a/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md +++ b/aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md @@ -29,10 +29,10 @@ of access than FileZilla uses. named after this project, since it may end up deploying other projects on this Pi too (the reference `SlpSoftware` project's own pipeline may already have exactly this kind of account; check its `PI_MAIN_USERNAME` secret first and reuse it directly if it already has SSH shell access, rather than -creating a second one). Example name: `pi-deploy`. +creating a second one). Example name: `gitea-workflow`. ```bash -sudo useradd -m -s /bin/bash pi-deploy -sudo passwd pi-deploy +sudo useradd -m -s /bin/bash gitea-workflow +sudo passwd gitea-workflow ``` Each project deploying through this account gets its own subdirectory under its home (§ 1.4 already namespaces by project: `~/apps/slpmodularcms-/`), so one generic account can serve multiple