stuff

human_script.md

@@ -258,7 +258,6 @@ All web services depend on Caddy:
 - Vaultwarden (vipy)
 - Forgejo (vipy)
 - LNBits (vipy)
-- Personal Blog (vipy)
 - ntfy-emergency-app (vipy)
 
 ### Verification:
@@ -629,7 +628,7 @@ ansible-playbook -i inventory.ini infra/420_system_healthcheck.yml \
   -e "healthcheck_interval_seconds=30"
 
 # CPU temp with custom threshold
-ansible-playbook -i inventory.ini infra/nodito/40_cpu_temp_alerts.yml \
+ansible-playbook -i inventory.ini infra/430_cpu_temp_alerts.yml \
   -e "temp_threshold_celsius=75"
 ```
 
@@ -815,7 +814,47 @@ Manual verification:
 
 ## Layer 8: Secondary Services
 
-**Status:** 🔒 Locked (Complete Layer 7 first)
+**Goal:** Deploy auxiliary services that depend on the core stack: ntfy-emergency-app and memos.
+
+**Script:** `./scripts/setup_layer_8_secondary_services.sh`
+
+### What This Layer Does:
+- Deploys the ntfy-emergency-app container on vipy and proxies it through Caddy
+- Optionally deploys Memos on `memos-box` (skips automatically if the host is not yet in `inventory.ini`)
+
+### Prerequisites (Complete BEFORE Running):
+- ✅ Layers 0–7 complete (Caddy, ntfy, and Uptime Kuma already online)
+- ✅ `ansible/services_config.yml` reviewed so the `ntfy_emergency_app` and `memos` subdomains match your plan
+- ✅ `ansible/infra_secrets.yml` contains valid `ntfy_username` and `ntfy_password`
+- ✅ DNS A records created for the subdomains (see below)
+- ✅ If deploying Memos, ensure `memos-box` exists in `inventory.ini` and is reachable as the `counterweight` user
+
+### DNS Requirements:
+- `<ntfy_emergency_app>.<domain>` → vipy IP
+- `<memos>.<domain>` → memos-box IP (skip if memos not yet provisioned)
+
+The script runs `dig` to validate DNS before deploying and will warn if records are missing or pointing elsewhere.
+
+### Run the Script:
+```bash
+source venv/bin/activate
+cd /home/counterweight/personal_infra
+./scripts/setup_layer_8_secondary_services.sh
+```
+
+You can deploy each service independently; the script asks for confirmation before running each playbook.
+
+### Post-Deployment Steps:
+- **ntfy-emergency-app:** Visit the emergency subdomain, trigger a test notification, and verify ntfy receives it
+- **Memos (if deployed):** Visit the memos subdomain, create the first admin user, and adjust settings from the UI
+
+### Verification:
+- The script checks for the presence of Caddy configs, running containers, and Memos systemd service status
+- Review Uptime Kuma or add monitors for these services if you want automatic alerting
+
+### Optional Follow-Ups:
+- Configure backups for any new data stores (e.g., snapshot memos data)
+- Add Uptime Kuma monitors for the new services if you want automated alerting
 
 ---