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

Names the deployed instance slpsoftware, not the software itself

Browse Source 
SlpModularCms is the product; slpsoftware.nl is the customer running
it - the first one, and a fine stand-in for what a real deployment
looks like. Renamed the directories, systemd units, and backup paths
accordingly. Left the backup script's own filename alone since the
already-committed deploy-scp.yaml calls it by that exact name.
This commit is contained in:
Sluijsens
2026-07-28 22:16:04 +02:00
parent 843253888e
commit 97f18d00e5
3 changed files with 47 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidlc-docs/features/gitea-deployment-workflow/audit.md
+11
View File
@@ -1323,3 +1323,14 @@ by Infrastructure Design. U5 carries REF-U3-01's Umami origin gate plus FR-21 an
**Context**: OPERATIONS — Deployment Setup, directory naming convention change before final approval
---
## Deployment Setup — Instance-Specific Naming (slpsoftware, not slpmodularcms)
**Timestamp**: 2026-07-28T04:20:00Z
**User Input**: "omdat SLP Modular CMS voor meerdere klanten gebruikt kan worden is de mapnaam slpmodularcms niet logisch. kan je in de documentatie of een placeholder gebruiken of slpsoftware. slpsoftware is namenlijk mijn eigen site en de eerste gebruiker dus een prima voorbeeld om te gebruiken"
**AI Response**: "Correct distinction: SlpModularCms is the software (multi-tenant capable), slpsoftware.nl is this specific customer instance. Renamed all instance-scoped naming (directories under ~/apps/ and /mnt/storage1/www/html/, systemd unit names, backup directory, backup credentials file, DB_NAME examples) from slpmodularcms to slpsoftware throughout deployment-instructions.md and rollback-plan.md. Left unchanged what's genuinely software-level, not instance-level: the backup script's own filename (backup-slpmodularcms-db.sh, matching the actual hardcoded reference in the already-committed deploy-scp.yaml), the SlpModularCms.Api.dll binary name, the systemd Description= string, and JwtSettings Issuer/Audience (existing app-config convention from README.md, unrelated to this feature). Added a naming note at the top of deployment-instructions.md explaining the instance-vs-software distinction for future customers."
**Context**: OPERATIONS — Deployment Setup, instance-naming correction before final approval
---