Frontend Deploy

Pipeline

Code
push to main
     |
     v
GitHub Actions triggered (separate workflows for dashboard and platform)
     |
     v
Build step:
  - npm ci
  - Vite build (VITE_* env vars injected at build time)
     |
     v
Upload dist/ to AWS S3
     |
     v
CloudFront cache invalidation (/* )
     |
     v
Live

Dashboard vs Platform

The dashboard (twin-dashboard-frontend) and platform (twin-platform-frontend) are deployed by separate GitHub Actions workflows. Each has its own S3 bucket and CloudFront distribution.

Environment Variables

Critical: Vite embeds VITE_* environment variables at build time, not runtime. This means:

• Env vars must be available when vite build runs in GitHub Actions.
• They are baked into the JavaScript bundle.
• Doppler is NOT used for frontend -- frontend uses GitHub Secrets.

GitHub Secrets Setup

For each VITE_* variable, add corresponding GitHub Secrets:

These are passed in the env: block of the Build step in .github/workflows/deploy.yml.

Staging vs Production

• Staging: Triggered on push to develop (or manually). Uses STAGING_* GitHub Secrets.
• Production: Triggered on push to main (or manually). Uses PRODUCTION_* GitHub Secrets.

Each environment has its own S3 bucket, CloudFront distribution, and API URL.

Troubleshooting