5.1 KiB
Infrastructure Design Plan - Unit 3: Hosting and targets
Feature: prerendering. Unit: 3 "hosting-and-targets" (see execution-plan.md § Units of Work). Builds on unit 1 (code summary) and unit 2 (code summary, measurement). Artifacts: infrastructure-design/.
No questions were needed. The owner and main session decided the open points on 2026-11-01; they are recorded as O1 to O9 in infrastructure-design.md section 14.
Functional Design is skipped for this unit (execution plan); its rules (BR-HST-xx) and testable properties (PBT-01) are recorded in infrastructure-design.md. NFR Design is skipped; the logical components are the generated server configuration, the preview server, the CI jobs and the Lighthouse configuration.
Category coverage
| Category | Applicability | Where |
|---|---|---|
| Deployment environment | Applies: test nginx on two Pis, production IIS on a shared webhost, preview server | infrastructure-design §2, §7; deployment-architecture §1 |
| Compute infrastructure | Applies: the web servers' rules; no sizing or scaling for a static site | infrastructure-design §4 |
| Storage infrastructure | N/A: static files only, no database or uploads | - |
| Messaging infrastructure | N/A: no queues or events | - |
| Networking infrastructure | Applies: reverse proxy Pi, HTTP/1.0 upstream and compression, redirects behind the proxy, FTPS | infrastructure-design §2.2, §4.2; deployment-architecture §1, §3 |
| Monitoring infrastructure | Applies narrowly: post-deploy script; no new tooling | deployment-architecture §8 |
| Shared infrastructure | Applies: the hosting Pi also runs WordPress; the global nginx.conf is not assumed |
infrastructure-design §4.2, §13 |
Steps
- Step 1: Read the artifact rules (infrastructure-design, mermaid standards, content validation) and the requirements (FR-PR-14 to 18, 23; NFR-PR-P-01, P-02, S-01), execution plan and application design
- Step 2: Read unit 1 (BR-404-07, BR-SRV, code summary, verification log with the
/Over-Mijand/over-mij/observations) and unit 2 (code summary, measurement) - Step 3: Read
serverConfig.tsand its test,previewServer.ts,securityHeaders.ts,pageFiles.ts,web/deploy/,lighthouserc.cjs,lighthouserc.desktop.cjs, the CI workflow and the frontend-shell operations documents - Step 4: Check the live test and production hostnames with read-only
curl(compression, server, status); the hosting Pi address is not reachable from this PC - Step 5: Spike in Chrome: case-sensitive server over the real
dist/client, today's rule against a canonical-redirect rule for/Over-Mij,/over-mij/,/soorten-fotoshoots/, query kept - Step 6: Check the installed router (
caseSensitive,trailingSlash) and Lighthouse 12.6.1 (ignoreStatusCode,errors-in-console) innode_modules, read only - Step 7: Design the URL contract (BR-HST-01 to 08), the nginx and IIS rules, the directory trap and the redirect safety rules
- Step 8: Settle the compression cause as far as the evidence allows, design nginx and IIS compression (BR-HST-09 to 11) and write the Pi diagnosis commands
- Step 9: Record the IIS unknowns (lock table, questions Q1 to Q6) and the "Before go-live on IIS" list; the probe kit, fallback variants and rule simulator were withdrawn by the owner because no host exists (BR-HST-19)
- Step 10: Design the deployment: upload order,
web.configplacement, guard,deploy-test, post-deploy script, nginx rollout order and rollback (BR-HST-14 to 18; deployment-architecture) - Step 11: Design the Lighthouse targets, the 404 audit route and the owner-decision feed (BR-HST-21 to 23)
- Step 12: Record testable properties (P-HST-01 to 11) and the recommendation for proving nginx rules without a production server (BR-HST-24)
- Step 13: Write
infrastructure-design.mdincluding Human tasks, To verify in code generation, owner decisions and compliance notes - Step 14: Write
deployment-architecture.mdwith topology, upload order, nginx rollout, verification matrices and rollback - Step 15: Check diagrams against the Mermaid standards and the content validation rules (Mermaid only, ids without hyphens, quoted labels, classDef with fill, stroke and
color:#000, one text alternative after each diagram) - Step 16: Create this plan and report to the orchestrator
Not changed: application code, configuration, audit.md, aidlc-state.md, requirements.md; nothing installed, deployed or committed; no Lighthouse run; no login anywhere.
- Step 17: Apply the owner and main-session decisions of 2026-11-01 (no IIS tooling,
numberOfRuns: 1, O1 to O9) and update properties and verification list - Step 18: Apply the Pi-Main findings: gzip off on the hosting Pi (candidate B confirmed), nginx 1.30.6 version gap, vhost path
/etc/nginx/conf.d/andreaslop-test.conf,server-opsdraft process for H2