Deployment Guide

This guide covers deploying extension builds, backends, and the docs site.

Extension Builds

Command	Output	Store
pnpm build:chrome	apps/extension/dist	Chrome Web Store
pnpm build:firefox	apps/extension/dist	Firefox Add-ons
pnpm build:edge	apps/extension/dist	Microsoft Edge Add-ons
pnpm build:safari	Xcode project (macOS)	App Store / Safari Extensions Gallery

Zip the apps/extension/dist folder and upload to each store. See Store Submission for review and packaging details.

Supabase Backend

1. Link project: supabase link
2. Set secrets: supabase secrets set STRIPE_API_KEY=... (etc.)
3. Deploy edge functions:

   cd apps/supabase
   supabase functions deploy stripe-checkout
   supabase functions deploy stripe-manage-subscription
   supabase functions deploy handle-stripe-webhook

4. Configure env in Vite (envs/.env.production) for production builds.

Firebase Backend

1. Set project: firebase use <project-id>
2. Deploy functions:

   cd apps/firebase
   pnpm deploy

3. Configure Stripe webhook, Resend, and Firebase config for production.

Docs Site

From the site monorepo:

cd site
pnpm build
pnpm deploy  # or docusaurus deploy, depending on your setup

For GitHub Pages or similar, see Docusaurus deployment docs.

Store Submission (Summary)

• Chrome Web Store – Zip dist/, upload to Chrome Web Store Developer Dashboard
• Firefox Add-ons – Zip dist/, submit at addons.mozilla.org
• Edge Add-ons – Submit at Partner Center (Chromium build; no extra packaging)
• Safari – Use pnpm build:safari; follow the Safari guide for App Store Connect

CI/CD Option

A GitHub Actions workflow can build on release:

1. On push to main or tag (e.g. v1.0.0): run pnpm quality:check and pnpm build:chrome
2. Optionally: deploy Supabase/Firebase functions if secrets are configured
3. Attach the built extension zip as an artifact for manual store upload

No implementation is provided by default; add workflows as needed for your release process.