mirror of
https://github.com/dong-nz/cv.git
synced 2026-11-22 16:10:40 +07:00
perf(edit): load the draft documents as one concurrent wave
EditModeShell issued the 12 draft documents with a for-loop of awaits, then the 2 category-label files. It now starts two concurrent requests whose success and failure handlers are attached in the same tick, so a label rejection landing while the documents are still in flight is not an unhandled rejection. The two failure branches are unchanged: a document failure is the offline state, a label failure only disables the category rule. Measured through the dev proxy, the same transport the app uses: 12 documents sequential 902 ms -> 210 ms for the whole 14-request wave, 38768 bytes and 12 distinct payloads byte-identical to the sequential loop. nginx.conf now proxies /api/content/ to Gitea over HTTP/2 (proxy_http_version 2 + a cleared Connection header), so the wave rides one pooled upstream connection instead of one HTTP/1.1 connection per in-flight request. The stack's nginx 1.31.x already does HTTP/1.1 with upstream keepalive caching by default since 1.29.7, so no upstream block is declared and the envsubst contract is untouched; the pipeline's test-before-touch nginx -t is what proves the image accepts proxy_http_version 2. Specs: spec-v4-live-edit.md row 25 + the draft-initialization bullet, spec-v4-deploy-infra.md D14 + row 10, AGENTS.md nginx.conf line.
This commit is contained in:
1 parent
3126971852
commit
83da513931
5 files changed
+43
-12
No files matched your search
@@ -145,7 +145,7 @@ src/
|
||||
- Site deployment is triggered automatically by gitea workflow `.gitea/workflows/deploy.yml` (push to `master`); infra redeployment by `.gitea/workflows/deploy-infra.yml` — triggered ONLY by changes to `nginx.conf` / `compose.yaml` / `deploy/htpasswd`, plus `workflow_dispatch` (the token-rotation runbook): test-before-touch (`nginx -t` in a throwaway container with placeholder values), then `docker compose up -d --force-recreate` + health probe (spec: `docs/design/specs/v4/spec-v4-deploy-infra.md`)
|
||||
- Site identity is deployment-time configuration, not a repo literal: `SITE_URL` / `SITE_NAME` are Gitea Actions **variables** (`vars.` context — public values, not secrets) passed as job env to `build` and `generate-resume`; locally they live in the uncommitted `.env` (template `.env.example`). A production build without them fails with an error naming the variable
|
||||
- Three jobs: `build` (`pnpm build` → `dist/` artifact) → `generate-resume` (`pnpm tsx scripts/generate-resume.ts --lang=en`, then `--lang=vi`) → `deploy` rsyncs `dist/`, both PDFs included, to `/opt/stacks/dong-site/dist/`
|
||||
- `nginx.conf` — production Nginx SPA routing + caching config + the `/api/content/` location: auth_basic (`deploy/htpasswd`) in front of a proxied Gitea Contents API; the upstream URL and the write token are `${GITEA_CONTENTS_API}` / `${GITEA_TOKEN}` substituted by the image's envsubst step at container start — the token and the Gitea host never enter the SPA bundle or the repository
|
||||
- `nginx.conf` — production Nginx SPA routing + caching config + the `/api/content/` location: auth_basic (`deploy/htpasswd`) in front of a proxied Gitea Contents API, proxied to it over HTTP/2 (`proxy_http_version 2` + a cleared `Connection` header, spec D14; the stack's nginx 1.31.x already caches upstream connections by default since 1.29.7, so no `upstream` block is declared, and the template still carries only `${GITEA_CONTENTS_API}` / `${GITEA_TOKEN}` — the token and the Gitea host never enter the SPA bundle or the repository)
|
||||
- `compose.yaml` — the stack definition for local AND VPS use (repo copy == stack copy): runtime values live in `secrets/site_config` (gitignored file in the stack directory, two lines `GITEA_TOKEN=` / `GITEA_CONTENTS_API=`, chmod 600), sourced by an entrypoint override (`set -a` + inline `nginx -g 'daemon off;'` — a compose entrypoint override drops the image's CMD) before the official entrypoint renders the template; the stack directory has no `.env`. On the VPS the same stack is managed by **Dockge** (upstream; stacks dir `/opt/stacks`, stack file `/opt/stacks/dong-site/compose.yaml`) — the repository is the single source of truth for `nginx.conf` / `compose.yaml` / `deploy/htpasswd`
|
||||
- `compose.override.yaml` — local-only, auto-merged by `docker compose`, never rsynced by the pipeline: publishes the container on `127.0.0.1:8081` so the production stack can be browsed locally; the VPS stack is unaffected
|
||||
|
||||
|
||||
Reference in new issue
Block a user