Weekly Planner
Getting started

Environment variables

App, Instant, Vercel, and CI environment variables used by Weekly Planner.

Environment variables

Copy .env.example to .env for local work.

Required for full local/API behavior

VariableUsed byPurpose
INSTANT_APP_IDInstant CLI, Vercel APIsSame value as src/config.jsAPP_ID. Also accepted as VITE_INSTANT_APP_ID in API routes.
INSTANT_ADMIN_TOKENpush:*, /api/invite, /api/share-metaInstant admin SDK. Set in Vercel Preview and Production.

Auth origins (previews)

VariableUsed byPurpose
INSTANT_CLI_AUTH_TOKENsync:auth-origins, GitHub ActionFrom npx instant-cli@latest login -p. Do not commit.
VERCEL_PROJECT_NAMEsync scriptDefaults to repo slug weekly-planner.
INSTANT_AUTH_WEBSITE_URLsync scriptOptional custom domain for website origin.

Open Graph / site URL

VariableUsed byPurpose
SITE_URLVite build pluginAbsolute origin for og:image / canonical. On Vercel, VERCEL_PROJECT_PRODUCTION_URL / VERCEL_URL are used when unset.

Browser vs server

  • Browser Instant client reads APP_ID from src/config.js (not Vite import.meta.env).
  • Serverless routes read Instant credentials from process env.
  • Theme, print prefs, share unlocks, and legacy migration use localStorage / sessionStorage keys defined in src/config.js — not env vars.

Docs site

The Fumadocs app under docs/ needs no Instant or app secrets to build or deploy.

On this page