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>
Jobs now pick runners by label: check and Lighthouse run on any Linux runner,
deploys only on the Pi. The test deploy is listed before Lighthouse, so a single
runner deploys first while two runners run both at once.
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>
`scp -r dist/.` also sets the mode of the target folder, which only its
owner may do. Copying the contents (`dist/*`, with dotglob for hidden
files) leaves the folder itself alone, so group write access on the test
folder is enough.
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>