Deploys to test without waiting for Lighthouse

Test exists to try things out, so it now deploys as soon as the check
job passes; Lighthouse runs alongside and its reports are information.
Production still waits for both check and Lighthouse, so accessibility,
best-practices and SEO problems never go live.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 09:01:45 +02:00
co-authored by Claude Opus 5.5
parent fccc909660
commit a87602ef5a
3 changed files with 42 additions and 2 deletions
@@ -702,3 +702,39 @@ Verder heb ik de vraag ook beantwoord"
**Context**: OPERATIONS - Deployment Setup; fixing CI
---
## Deployment Setup - PR Green and Merged
**Timestamp**: 2026-10-18T23:42:04Z
**User Input**: "(none — monitoring as authorised)"
**AI Response**: "Run 530 (PR #3, 23f7020): check and lighthouse succeeded. PR #3 auto-merged by the owner (merge commit fccc909). Run 531 (push to master) started with deploy-test; watching it."
**Context**: OPERATIONS - Deployment Setup; watching first master run
---
## Deployment Setup - First Master Run 531
**Timestamp**: 2026-10-19T00:01:36Z
**User Input**: "(none — monitoring as authorised)"
**AI Response**: "Run 531 (push to master, fccc909): check and lighthouse succeeded; deploy-test reached the Pi (SSH login with secrets OK, WordPress guard passed) but failed on 'mkdir: cannot create directory /var/www/html/andreaslop-test: Permission denied'. Cause: folder missing and /var/www/html owned by root (deployment-instructions 1.2.1 not yet done). Not solved with sudo in the pipeline (would widen deploy-user rights). Asked owner to create and chown the folder once, then re-run."
**Context**: OPERATIONS - Deployment Setup; awaiting owner action on the Pi
---
## Deployment Setup - Lighthouse After Test Deploy
**Timestamp**: 2026-10-19T07:01:45Z
**User Input**: "Ja, voer maar door, maar wacht met een PR maken totdat de huidige run de deploy-test job heeft afgerond. Ik heb voor PR's bewust alleen de check job aangegeven omdat ik dacht dat lighthouse vooral belangrijk is voor productie om te blokkeren en voor test is het info waar je eventueel op kan reageren als je het lokaal vergeten bent bijvoorbeeld. Voor nu hoeft het niet als check voor mergen naar master."
**AI Response**: "Owner re-ran run 531 after creating the test folder via a symlink (/var/www/html -> /mnt/storage1/www/html; explained symlink permissions are ignored, target folder rights count). Fast-forwarded feature/frontend-shell to master (fccc909). Workflow: deploy-test now needs only check (Lighthouse runs alongside as information); deploy-production still needs check and lighthouse. Deployment plan D6 updated incl. branch protection (only check required, Lighthouse deliberately not). Pushing to the feature branch; PR to be created after run 531's deploy-test finishes."
**Context**: OPERATIONS - Deployment Setup
---