Redirects www to andreaslop.nl and closes out the front-end shell
Continuous Integration / check (pull_request) Successful in 6m9s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 12m16s
Continuous Integration / deploy-production (pull_request) Skipped

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>
This commit is contained in:
2026-10-19 16:14:26 +02:00
co-authored by Claude Opus 5.5
parent 62a88e12f5
commit c24f629869
9 changed files with 203 additions and 11 deletions
@@ -123,10 +123,14 @@ git rm --cached -r -q . && git reset --hard
- an unknown URL (the 404 page)
- the five security headers (`curl -sI`)
- that HTTP redirects to HTTPS
- that `www.andreaslop.nl` (also add it to the `hosts` entry) redirects with 301 to `https://andreaslop.nl/` in one step, path included
- Remove the `hosts` entry afterwards.
2. Switch the DNS of `andreaslop.nl` (and `www`) to the new host, and make sure HTTPS is active.
3. Set `HEALTH_CHECK_URL_PRODUCTION` so every deploy is checked from then on.
4. Verify the live headers: `curl -sI https://andreaslop.nl/` must show all five security headers.
2. **Privacy statement first (blocking).** The privacy statement page must mention Umami (anonymous, cookieless, self-hosted in the Netherlands) and Sentry (error reports without IP address or personal data, EU region). Do not switch the DNS before it does.
3. Switch the DNS of `andreaslop.nl` and `www` to the new host, and make sure HTTPS is active for both (the certificate must cover `www`, otherwise the redirect shows a certificate error first).
4. Set `HEALTH_CHECK_URL_PRODUCTION` so every deploy is checked from then on.
5. Verify the live headers: `curl -sI https://andreaslop.nl/` must show all five security headers.
6. Add the UptimeRobot deep-link monitor for `https://andreaslop.nl/portfolio` (monitoring-setup §3).
7. Check the monitoring on production: a test error in the console arrives in Sentry under `production`, and a visit shows in Umami's production website.
## 3. If something fails