Deployment¶

Each component deploys independently from its own repository. This page summarizes how; the command-level detail, build variables and pipeline flows live in each project's section and repo.

Deployment per component¶

Component	How it deploys	CI/CD
Website	wrangler deploy to Cloudflare Workers	GitHub Actions (push to master/main) + per-branch previews
Platform	wrangler deploy to Cloudflare Workers	GitHub Actions (test.yml, deploy-preview.yml)
AI	wrangler deploy to Cloudflare Workers	GitHub Actions (test.yml, manual or CI deploy per repo)
App	Docker image (GHCR) → Kubernetes via Argo CD	GitHub Actions (build.yml); master→idk-dev, semver tag→idk-prod
Blog / CMS	Git push to Pantheon (Composer --no-dev) + Quicksilver hooks	GitHub Actions (sync_pantheon_master.yml)

Notes¶

• The three Cloudflare Workers (Website, Platform, AI) deploy with wrangler and get per-branch preview aliases from deploy-preview.yml.
• The App ships as a container image promoted through environments by Argo CD: master builds deploy to idk-dev; a semver tag promotes to idk-prod.
• WordPress deploys by pushing to Pantheon; Quicksilver hooks run on deploy (including New Relic deploy markers and Cloudflare cache purge).