slp-modular-cms

3 Commits

Include renames

Author	SHA1	Message	Date
SluijsensandClaude Sonnet 5	56f4f6fe0f	Adds Monitoring Setup docs and deploy-scp troubleshooting/debug fixes Continuous Integration / config (pull_request) Successful in 9s Details Continuous Integration / backend-build (pull_request) Successful in 4m27s Details Continuous Integration / vulnerability-scan (pull_request) Successful in 4m10s Details Continuous Integration / backend-test (pull_request) Canceled after 0s Details Continuous Integration / frontend-build (pull_request) Canceled after 0s Details Continuous Integration / frontend-test (pull_request) Canceled after 0s Details Continuous Integration / frontend-lint (pull_request) Canceled after 0s Details Continuous Integration / publish-test (pull_request) Canceled after 0s Details Continuous Integration / publish-production (pull_request) Canceled after 0s Details Continuous Integration / deploy-test (pull_request) Canceled after 0s Details Continuous Integration / deploy-production (pull_request) Canceled after 0s Details Continuous Integration / frontend-prepare (pull_request) Canceled after 50s Details Monitoring Setup: operations/plans/monitoring-setup-plan.md and operations/monitoring/monitoring-instructions.md, covering Sentry alert rules on the security_event tag, UptimeRobot's 6 liveness monitors, and the two new Umami website entries for the admin SPA. deployment-instructions.md gains a missing Observability__Environment host var (without it, both environments would tag Sentry events as "Production"), the nginx client_max_body_size fix for the 413 seen on publish-test/production artifact uploads, and two troubleshooting notes on Gitea Actions re-run behaviour: re-running deploy-test/production alone loses the run's uploaded artifact, and re-running all jobs on an existing (rather than a brand new) run can replay stale secrets. deploy-scp.yaml: step names no longer show literal unresolved ${{ inputs.* }} text (Gitea doesn't interpolate that context in step names), and a temporary debug step logs PI_MAIN_USERNAME/PASSWORD length plus a username equality check to diagnose a persistent Permission denied during the SSH steps, without ever logging the secret values themselves. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015FffvxxJp5wG34Ru48GBig	2026-07-29 19:39:44 +02:00
Sluijsens	2cd8c4aa88	Renames the backup script to match the instance, not the software Continuous Integration / config (pull_request) Successful in 10s Details Continuous Integration / backend-build (pull_request) Successful in 4m6s Details Continuous Integration / vulnerability-scan (pull_request) Successful in 3m39s Details Continuous Integration / frontend-prepare (pull_request) Failing after 58s Details Continuous Integration / frontend-build (pull_request) Skipped Details Continuous Integration / frontend-test (pull_request) Skipped Details Continuous Integration / frontend-lint (pull_request) Skipped Details Continuous Integration / backend-test (pull_request) Successful in 4m26s Details Continuous Integration / publish-test (pull_request) Skipped Details Continuous Integration / publish-production (pull_request) Skipped Details Continuous Integration / deploy-test (pull_request) Skipped Details Continuous Integration / deploy-production (pull_request) Skipped Details backup-slpmodularcms-db.sh named the CMS; this backs up slpsoftware specifically, same as every other instance-scoped path already does. Hardcoded in deploy-scp.yaml itself, so this is the actual pipeline code, not just docs describing it.	2026-07-29 14:17:41 +02:00
Sluijsens	bd2a963498	U6 — the deploy workflow itself deploy-scp.yaml: download, back up the production database before touching anything, upload into a timestamped release, symlink the persistent website in, switch current and restart, verify /health with retries, prune old releases only once that check passes. No sudo, no container actions, one shared interface U5 will call next.	2026-07-28 15:33:03 +02:00