cloud-deploy-gcp-aws

# Cloud Deploy — GCP & AWS (web) ## Overview A web deploy's shape follows the **render mode**, not the framework. Server-rendered (Next.js SSR, SvelteKit node) ships a container exactly like a backend; a static export (`next export`, Vite build) ships files to object storage behind a CDN. Pick the mode first. Read [[ci-cd-pipeline-authoring]] for the workflow naming/dispatch contract this fills in. **Core principle:** Match the deploy target to the render mode, bake public config at build time, and invalidate the CDN on every deploy — a stale edge cache is the most common "I deployed but nothing changed." ## Pick the target, then copy the boilerplate `search_boilerplate_catalog` → `deploy gcp web` / `deploy aws web`. Copy its `deploy-stage/preprod/prod.yml` into `.github/workflows/` as `<id>-deploy-<env>.yml`, then set the README's repo/environment **vars**. OIDC auth, no keys. ## SSR (containerized) Same path as the backend deploy: build the image, push, deploy to **Cloud Run** (GCP) or **App Runner/ECS** (AWS), smoke-test the URL. Use this when the app has server components, API routes, or ISR. See [[cloud-deploy-gcp-aws]] in the backend skill set for the container mechanics. ## Static (object storage + CDN) - **GCP:** either **Firebase Hosting** (`firebase deploy --only hosting`, simplest, CDN + rollback built in) or a **GCS bucket + Cloud CDN / load balancer**; after upload, invalidate the CDN. - **AWS:** sync the build output to an **S3** bucket and serve via **...