The deployment plan still said branch protection only required check.
The owner made lighthouse a required check on 2026-10-19.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
IIS now sends www.andreaslop.nl to https://andreaslop.nl in one step, so
monitoring and search engines see a single address. The go-live steps check
the redirect and wait for the privacy statement, and the readiness checklist
lists what is left for the go-live.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sentry loads after the page and reports errors only, without personal data;
Umami counts visits per environment. Both only run on andreaslop.nl and
test.andreaslop.nl. The CSP allows just these two hosts, and builds carry the
commit SHA as release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Monitoring reuses the existing Sentry organisation, the self-hosted
Umami instance and UptimeRobot, with e-mail alerts. One build serves
both environments; the browser picks test or production from the
hostname and sends nothing on other hosts. Sentry captures errors only,
loads after the page and stores no personal data. Code changes follow
after approval.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pipeline logs in as gitea-workflow, a member of the www-data group.
The test folder needs group write access (775, or 2775 with setgid);
new folders get 755 by default, which made the first deploys fail.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
Lighthouse slows the CPU 4x relative to the measuring machine, so the
Raspberry Pi runner scores performance 30-40 points lower than a PC for
the same build. In CI the performance assertions now only warn;
accessibility, best practices and SEO still block, and performance still
blocks in `pnpm check` on a PC. Mobile and desktop reports go to
separate folders and are attached to every run as an artifact.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pipeline runs lint, format, tests, build, dependency audit and
Lighthouse (mobile and desktop, Playwright Chromium on the arm64 runner)
on every pull request, push to master and manual run.
Pushes to master deploy to test automatically, and any branch can be
deployed to test manually. Test is a Raspberry Pi with nginx next to the
current WordPress site; the deploy refuses folders containing WordPress.
Production deploys are manual and only from release/* branches, over
FTP with TLS to the IIS webhost.
The IIS web.config and both nginx configs are generated from the same
security header list as the Vite servers, with a test that fails when
the generated files drift. Adds .gitattributes for LF line endings and
pins pnpm through packageManager.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>