Files

3.0 KiB

Application Design (consolidated) - andreaslop-site-hosting

Details: components.md, component-methods.md, services.md, component-dependency.md.

Decisions

# Decision Source
D1 CmsHostOptions.WebsiteMode (SpaFallback default, PrerenderedPages); existing clients unchanged Brief, FR-U1-01
D2 All nginx-parity rules live in one pure WebsitePathResolver taking a file-exists predicate; the middleware is a thin adapter Requirements FR-U1-02
D3 A page is "known" by a per-request file-exists check on the lowercased name; no cache, no restart needed after a site delivery Q2 = A
D4 StrictSite policy in CspPolicyCatalog, byte-identical to the site's current CSP; origins from new AllowedSiteScriptOrigins / AllowedSiteConnectOrigins, so admin policies stay as strict as today Q1 = A
D5 Compression only for non-reserved paths; /api/v1 and /admin not compressed by this feature Requirements open point 5
D6 Unknown website paths get 404.html with status 404 in a final pipeline stage after API routes; an unknown /api/v1 path stays an API 404 FR-U1-03/04/10
D7 Setup token: Identity:Setup:Token optional, header X-Setup-Token, constant-time compare, GET /Setup/status returns tokenRequired, setup page shows the field only when required Q3 = A, FR-U2-07
D8 Theme is a build-time CSS override of existing tokens (VITE_THEME), language default via VITE_DEFAULT_LANGUAGE; no runtime theme API Brief D2, Q5
D9 Module set of the Andrea client = its project references; Availability included only if the admin needs it (decided in U2 NFR/Code Generation, reported to the requester) Brief D1
D10 Unit order: U1 Core (with regression run), hand-back and wait for the requester's "go", then U2 Brief, execution plan

Risks carried into Construction

  1. The existing security-header writer treats CSP/frame/referrer as HTML-only; website 301/asset/robots responses may need the full set (FR-U1-09). Settled in U1 Functional Design with tests.
  2. UseHttpsRedirection on plain HTTP behind the proxy Pi, and absent forwarded-headers handling: verify no loop or absolute http:// redirect (website redirects are relative).
  3. Per-request File.Exists on a Pi SD card or /mnt/storage1: low cost expected; measured in U1 NFR Design.
  4. Setup endpoints and rate limiting: confirm the login limiter covers /Setup/owner (NFR Design U2).
  5. Frontend setup page change touches an existing screen (small, covered by tests).

Security Baseline / PBT applicability (design stage)

  • Security: path input validation centralised in one pure function; secure-by-default configuration (new settings default to today's behaviour); no secrets in repo (token and DB password come from the environment); constant-time token compare; no new dependencies. Compliant / N/A items are tabulated in the NFR stages.
  • PBT (partial): the resolver (PBT-02/03 invariants), canonical idempotence, policy round trip are pure and directly testable.