SLP_Software/slp-modular-cms
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity
82 Commits 1 Branch 0 Tags
56f4f6fe0f6c57c8982d06e8fd71b93e17e9755d
Commit Graph
3 Commits
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 2f243f23c3 Fixes the account model deploy setup got wrong 
webadmin turned out to be FTP-only and belongs to whoever uploads
customer websites, not to this pipeline. Switched to a separate
deploy account with its own home-directory paths, well away from
where the other sites live, and made the persistent website symlink
cross into webadmin's territory instead of the other way around.
 2026-07-28 19:41:34 +02:00
Sluijsens cf80f827ae Deployment setup - the parts the workflow deliberately left out 
Host setup checklist, real domains and ports, the database backup
script the deploy workflow only ever invokes, and a rollback plan.
Also drafted the FTPS switch procedure for whenever production moves
off the Pi, with a note that shared hosting is likely IIS-based -
that's a bigger change than swapping the transport.
 2026-07-28 19:07:26 +02:00