Redirects www to andreaslop.nl and closes out the front-end shell
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:
@@ -942,3 +942,49 @@ Verder heb ik de vraag ook beantwoord"
|
||||
**Context**: OPERATIONS - Deployment pipeline adjustment verified
|
||||
|
||||
---
|
||||
|
||||
## Monitoring Setup - Approval
|
||||
|
||||
**Timestamp**: 2026-10-19T13:02:24Z
|
||||
|
||||
**User Input**: "helemaal goed. ga door naar Production Readiness"
|
||||
|
||||
**AI Response**: "Monitoring Setup marked approved (Sentry + Umami verified on test: Sentry event in environment test with the commit as release, owner saw it and resolved it; Umami counted the owner's own visit, headless Chrome is ignored as a bot). Started Production Readiness Validation: not a .NET project (no .csproj, api/ empty), so the appsettings check is skipped. Rollback (rollback-plan.md), backups (static site, nothing to back up), secrets (Gitea secrets; DSN/Umami IDs public by design) and alert ownership (owner, Q7 = A) are covered. Open gaps put in operations/plans/production-readiness-questions.md: production dress rehearsal, www.andreaslop.nl, incident runbook, SSH password for deploy-test, privacy statement before go-live."
|
||||
|
||||
**Context**: OPERATIONS - Monitoring Setup complete; Production Readiness Validation started, awaiting answers
|
||||
|
||||
---
|
||||
|
||||
## Production Readiness Validation - Answers
|
||||
|
||||
**Timestamp**: 2026-10-19T13:49:14Z
|
||||
|
||||
**User Input**: "ik heb de vragen beantwoord"
|
||||
|
||||
**AI Response**: "Answers: Q1 B ('want ik heb de hosting nog niet dus kan dat nog niet testen'), Q2 A, Q3 B, Q4 B, Q5 A. Implemented Q2: web.config redirects www.andreaslop.nl with 301 to https://andreaslop.nl in one step (rule before HTTPS; productionHost in serverConfig.ts; tests for the rule, its order and that the target is the monitored production host); regenerated web.config; lint, format, typecheck, 111 tests and build green. Deployment instructions go-live: www check in the dress rehearsal, privacy statement as blocking step before the DNS switch (Q5 A), certificate must cover www, post-go-live monitoring checks. Created operations/production-readiness-checklist.md. Not committed (commit/push only on request)."
|
||||
|
||||
**Context**: OPERATIONS - Production Readiness Validation
|
||||
|
||||
---
|
||||
|
||||
## Production Readiness Validation - Complete
|
||||
|
||||
**Timestamp**: 2026-10-19T13:49:14Z
|
||||
|
||||
**Overall Readiness**: Yes with caveats (production go-live belongs to the feature that fills the pages; hosting not yet available)
|
||||
|
||||
**Feature Status**: Complete
|
||||
|
||||
---
|
||||
|
||||
## Production Readiness Validation - Commit and Push
|
||||
|
||||
**Timestamp**: 2026-10-19T14:14:26Z
|
||||
|
||||
**User Input**: "heb je alle changes al gepusht" / "ja doe dat maar"
|
||||
|
||||
**AI Response**: "Committing the www redirect, go-live instructions, readiness checklist and questions, state, registry and audit, and pushing together with the local runner-docs commit to PR #4; watching the run until green."
|
||||
|
||||
**Context**: Feature complete; commit/push on request
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user