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

Feature/gitea deployment workflow #1

Merged
Sluijsens merged 35 commits from feature/gitea-deployment-workflow into master 2026-07-29 16:50:44 +02:00
Conversation 0 Commits 35 Files Changed 193
+17 -6
2 changed files with 17 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 73126f5a9c - Show all commits
aidlc-docs/features/gitea-deployment-workflow/aidlc-state.md
+6 -6
View File
@@ -68,9 +68,9 @@ Execution rounds (Q4 = B): **R1** = U1 + U2 · **R2** = U3 + U4 · **R3** = U5 +
- [x] Functional Design — **EXECUTE for U1, U2, U3, U4**; SKIP for U5, U6, U7. **U1 ✅ U2 ✅** approved 2026-07-27 · **U3 ✅ U4 ✅** 2026-07-28 - [x] Functional Design — **EXECUTE for U1, U2, U3, U4**; SKIP for U5, U6, U7. **U1 ✅ U2 ✅** approved 2026-07-27 · **U3 ✅ U4 ✅** 2026-07-28
- [ ] NFR Requirements — **SKIP (all units)** — already comprehensively captured in `requirements.md` § 5 and § 6 - [ ] NFR Requirements — **SKIP (all units)** — already comprehensively captured in `requirements.md` § 5 and § 6
- [x] NFR Design — **EXECUTE for U3, U4**; SKIP for the rest. *Deliberate deviation from the default NFR-Requirements/NFR-Design coupling — rationale in the execution plan.* **U3 ✅ U4 ✅** 2026-07-28 — 11 patterns for U3, 10 for U4. Closed OPEN-01; raised REF-U3-01 - [x] NFR Design — **EXECUTE for U3, U4**; SKIP for the rest. *Deliberate deviation from the default NFR-Requirements/NFR-Design coupling — rationale in the execution plan.* **U3 ✅ U4 ✅** 2026-07-28 — 11 patterns for U3, 10 for U4. Closed OPEN-01; raised REF-U3-01
- [ ] Infrastructure Design — **EXECUTE for U6, U7**; SKIP for the rest - [x] Infrastructure Design — **EXECUTE for U6, U7 per the original plan; SKIP for the rest**. **U6 ✅** 2026-07-28 — single Pi, directory-only environment split, `systemd --user` (no sudo), releases/current/shared layout, 2-release retention, health check via public URL. Raised INFRA-U6-01 (linger requirement, carried to Operations). **U7 did not need it in practice**: by Units Generation, U7's scope had narrowed to documentation-only (Q8 = A — operational/infrastructure decisions moved to Operations), so it went straight to Code Generation with no infrastructure to design
- [~] Code Generation — **EXECUTE** (all 7 units, each built and tested before its completion message). **U1 ✅ U2 ✅** 2026-07-27 (253 backend tests). **U3 ✅** 2026-07-28 (315). **U4 ✅** 2026-07-28 (366 backend + 237 frontend) - [x] Code Generation — **EXECUTE** (all 7 units, each built and tested before its completion message). **U1 ✅ U2 ✅** 2026-07-27 (253 backend tests). **U3 ✅** 2026-07-28 (315). **U4 ✅** 2026-07-28 (366 backend + 237 frontend). **U6 ✅ U5 ✅** 2026-07-28 — Round 3: `deploy-scp.yaml` + `continuous_integration.yaml`, 372 backend + 237 frontend tests (unchanged from Round 2, confirming no regressions from FR-21/FR-22 fixes), 0 vulnerable packages, lint clean. Raised REF-U5-01 (Umami-origin gate needs a parallel Gitea variable, since the backend side is a host env var per D-16). **U7 ✅** 2026-07-28 — Round 4: `WEBSITE_WORKSPACE.md`, README.md and `.env.example` updated, all claims re-verified against actual U1–U6 source. **All 7 units complete.**
- [ ] Build and Test — **EXECUTE** - [ ] Build and Test — **EXECUTE** (phase-level, now that all 7 units are complete)
### OPERATIONS ### OPERATIONS
- [ ] Deployment Setup — **EXECUTE** - [ ] Deployment Setup — **EXECUTE**
@@ -84,9 +84,9 @@ Execution rounds (Q4 = B): **R1** = U1 + U2 · **R2** = U3 + U4 · **R3** = U5 +
## Current Status ## Current Status
- **Lifecycle Phase**: CONSTRUCTION - **Lifecycle Phase**: CONSTRUCTION
- **Current Stage**: Round 2 complete — U3 Security Headers & CSP and U4 Observability generated, built and tested - **Current Stage**: Round 4 **closed** 2026-07-28 — U7 complete and committed (`88770c5`). All 7 units of work are now generated
- **Next Stage**: Round 3 — U5 CI Workflow & Gates + U6 Deploy Workflow (U6 needs Infrastructure Design first) - **Next Stage**: Build and Test (phase-level) — the last Construction stage before Operations
- **Status**: Round 2 **closed** 2026-07-28. Rounds 1 and 2 committed, nothing pushed. Awaiting approval to start Round 3 - **Status**: Rounds 1–4 all done, nothing pushed. Starting Build and Test
## Round 2 Design Record (2026-07-28) ## Round 2 Design Record (2026-07-28)
- Functional Design U3 + U4 complete and committed (`357d395`) - Functional Design U3 + U4 complete and committed (`357d395`)
aidlc-docs/features/gitea-deployment-workflow/audit.md
+11
View File
@@ -1181,3 +1181,14 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: CONSTRUCTION — Round 4 — U7 Code Generation complete, presenting completion message **Context**: CONSTRUCTION — Round 4 — U7 Code Generation complete, presenting completion message
--- ---
## Code Generation — U7 (Approved) / Round 4 Closed / All Units Complete
**Timestamp**: 2026-07-28T02:05:00Z
**User Input**: "Continue to Next Stage"
**AI Response**: "U7 approved and committed (88770c5). Round 4 closed — all 7 units (U1-U7) are now complete. Corrected aidlc-state.md: Infrastructure Design's original plan listed U7, but its scope narrowed to documentation-only by Units Generation, so it never needed the stage in practice. Proceeding to the phase-level Build and Test stage."
**Context**: CONSTRUCTION — all units complete; entering Build and Test
---