Configuration - Web

Getting Started to web frontend configuration in RedPanda.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

เริ่มใช้งานฟรี

Overview

The web (Vite + SvelteKit) is configured from:

web/.env.* environment files
web/src/web-config.json for PWA metadata

Note

Any change to environment values requires restarting your dev server. Local HTTPS and how VITE_API_BASE_URL interacts with the dev proxy are documented under Vite (SvelteKit).

Common setup steps

Configure your web env files

Copy web/.env.development.example to web/.env.development.local and fill in values (see the Vite env guide below).

Set production env values

Maintain web/.env.production.local from web/.env.production.example and set matching production values for your deployment. Set VITE_FRONTEND_DOMAIN_URL to the same canonical origin as the backend’s FRONTEND_DOMAIN_URL so OAuth redirect URIs stay consistent (see Vite (SvelteKit) and Production deployment).

For CLI device login browser routes (/cli/device/*), set server-only CLI_AUTH_SERVER_URL to your auth server API origin (RedPanda production: https://YOUR_CLI_AUTH_SERVER). See Configuration - Agent.

For Supabase region cutover or other maintenance windows, set server-only MAINTENANCE_MODE (off, banner, or freeze_writes). During freeze_writes, auth and app routes redirect to /maintenance while public SEO pages stay live. See Maintenance mode.