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/operations/deployment/rollback-plan.md
+3 -3
View File
@@ -16,10 +16,10 @@ failed deploy never leaves fewer than two releases on disk.
No rebuild needed. Over SSH, on the Pi:
```bash
cd ~/apps/slpmodularcms/<env>/releases
cd ~/apps/slpsoftware/<env>/releases
ls -1t # confirm which directory is the previous, working release
ln -sfn ~/apps/slpmodularcms/<env>/releases/<previous-timestamp> ~/apps/slpmodularcms/<env>/current
systemctl --user restart slpmodularcms-<env>.service
ln -sfn ~/apps/slpsoftware/<env>/releases/<previous-timestamp> ~/apps/slpsoftware/<env>/current
systemctl --user restart slpsoftware-<env>.service
curl -f https://<env-domain>/health # confirm the rollback itself is healthy
```