문제: 3f9c087은 초기 청크를 묶지 않는 근거로 "템플릿은 HTTP/2 이상으로 서빙한다"를 정했다. 그런데 이 전제는 작업 기록인 performance-evidence.md 에만 있다. 호스팅을 정하는 사람이 읽는 현재 계약 문서(static-delivery.md) 에는 서빙 프로토콜 이야기가 없다. 고른 방법: static-delivery.md 끝에 한 단락을 더한다. HTTP/2 이상으로 서빙한다는 것, HTTP/1.1에서 늦어지는 정도(Fast 3G 약 1초), HTTP/2에서의 차이(100 ms 미만), HTTP/1.1만 되는 제품이 할 일을 적고 측정 기록으로 링크한다. 버린 대안: README의 배포 절에 적기. README는 배포 변수와 명령을 다루고, 호스트 동작은 static-delivery.md가 다룬다. 위험·한계: 수치는 2026-11-03 한 번의 측정이다. 셸이 바뀌면 달라진다. 검증: node scripts/verify-documentation-readiness.ts PASS_SCOPED
52 lines
2.6 KiB
Markdown
52 lines
2.6 KiB
Markdown
# Static asset and runtime-config delivery
|
|
|
|
> **정본 안내 (non-authoritative for runtime capability decisions)**
|
|
>
|
|
> Runtime Config/boot, Fetch HTTP client, Router, Query/Mutation, realtime 공통 경계, Web Worker,
|
|
> Service Worker, offline command와 Background Sync의 구현 결정은
|
|
> [프론트엔드 런타임 Capability 저장소 정합형 구현 결정 폐쇄 상세 설계](./2026-07-30-frontend-runtime-capability-repository-aligned-implementation-closed-deep-design.md)가 정본이다.
|
|
> 본 문서의 해당 서술이 정본과 충돌하면 정본을 따른다.
|
|
|
|
|
|
This Mermaid view is a repository-local implementation projection. The
|
|
`PASS_SCOPED` reviewer evidence applies only to the canonical static-delivery
|
|
draw.io scope recorded in `review-ledger.json`.
|
|
|
|
```mermaid
|
|
sequenceDiagram
|
|
participant CI
|
|
participant ImmutableRelease
|
|
participant ActivePointer
|
|
participant Browser
|
|
CI->>ImmutableRelease: upload hashed assets
|
|
CI->>ImmutableRelease: upload release manifest
|
|
CI->>ImmutableRelease: upload runtime config
|
|
CI->>ImmutableRelease: probe asset reachability
|
|
CI->>ActivePointer: atomically switch HTML
|
|
Browser->>ActivePointer: fetch revalidated HTML
|
|
Browser->>ImmutableRelease: fetch no-store config and manifest
|
|
Browser->>ImmutableRelease: fetch immutable hashed assets
|
|
CI->>Browser: boot, route, API, and reload-loop smoke
|
|
```
|
|
|
|
In this repository the workflow deploys nothing. The upload, pointer switch
|
|
and smoke steps above belong to the project's provider adapter, which fills the
|
|
`deployment` job between `promotion` and `production_gate`. After it has
|
|
deployed the promoted release, FE-GATE-019 probes the live headers and checks
|
|
that the host serves that release; while the slot is empty FE-GATE-019 is
|
|
`UNVERIFIED` (reviews 13-05, 1101/13-01,
|
|
[`release-cache-rollback.md`](../operations/release-cache-rollback.md)).
|
|
|
|
Rollback changes the active pointer only after confirming that the prior
|
|
immutable release has a coherent HTML/assets/config/API/manifest tuple.
|
|
|
|
Serve the app over HTTP/2 or later. The entry preloads about 26 initial
|
|
JavaScript files in parallel. Over HTTP/1.1 they queue for six connections per
|
|
host, and the first screen on Fast 3G came about one second later than with the
|
|
initial chunks grouped (2026-11-03). Over HTTP/2 the difference was under
|
|
100 ms, so the template keeps the chunks split. A product that can only serve
|
|
HTTP/1.1 groups its initial chunks in `vite.config.ts` and measures again
|
|
whenever the shell changes ("초기 청크 수와 HTTP/1.1" in
|
|
[`performance-evidence.md`](../operations/performance-evidence.md), review
|
|
1101/14.4).
|