multica/apps/desktop/.env.example
Jiayuan Zhang 9e40e8ca76 chore: update reset scripts and docs for dev data directory
- dev:desktop:reset now cleans both ~/.super-multica and ~/.super-multica-dev
- reset-user-data.sh handles dev directory
- .env.example documents SMC_DATA_DIR

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-15 00:39:25 +08:00

106 lines
4.4 KiB
Text

# =============================================================================
# Multica Desktop Environment Configuration
# =============================================================================
#
# This file documents all available environment variables for Desktop builds.
# Copy this file and rename it based on your target environment.
#
# =============================================================================
# Build Commands
# =============================================================================
#
# Development (no .env file needed):
# pnpm dev # Uses hardcoded dev defaults
#
# Staging Build:
# pnpm build:staging # Uses .env.staging
#
# Production Build:
# pnpm build:production # Uses .env.production
#
# Default Build (uses .env.production):
# pnpm build:desktop # Same as build:production
#
# =============================================================================
# Build Output
# =============================================================================
#
# After build completes, installer packages are located at:
#
# apps/desktop/release/{version}/
# ├── Multica-{version}-arm64.dmg # macOS Apple Silicon
# ├── Multica-{version}-x64.dmg # macOS Intel
# ├── Multica-Windows-{version}-Setup.exe # Windows
# ├── Multica-Linux-{version}.AppImage # Linux AppImage
# └── Multica-Linux-{version}.deb # Linux deb
#
# Compiled code (before packaging) is in:
# apps/desktop/out/
#
# =============================================================================
# Configuration Guide
# =============================================================================
#
# For production builds, create .env.production with the following variables:
#
# Required:
# MAIN_VITE_GATEWAY_URL - WebSocket Gateway URL for remote connections
# MAIN_VITE_WEB_URL - Web App URL for OAuth login flow
# MAIN_VITE_API_URL - API URL bridged to process.env for core package
# RENDERER_VITE_API_URL - API URL for renderer process (UI requests)
# MULTICA_API_URL - API URL for core/tools (web-search, finance)
#
# Example .env.production:
# MAIN_VITE_GATEWAY_URL=https://gateway.multica.ai
# MAIN_VITE_WEB_URL=https://www.multica.ai
# MAIN_VITE_API_URL=https://api.multica.ai
# RENDERER_VITE_API_URL=https://api.multica.ai
# MULTICA_API_URL=https://api.multica.ai
#
# =============================================================================
# Variable Naming Convention
# =============================================================================
#
# MAIN_VITE_* - Main process only (Node.js, full system access)
# RENDERER_VITE_* - Renderer process only (browser context)
# VITE_* - All processes
# MULTICA_* - Core/CLI/Gateway (read via process.env at runtime)
#
# =============================================================================
# Environment Variables
# =============================================================================
# MAIN_VITE_GATEWAY_URL
# WebSocket Gateway URL - Hub connects here for remote device access (QR code pairing)
# Production example: https://gateway.multica.ai
MAIN_VITE_GATEWAY_URL=http://localhost:3000
# MAIN_VITE_WEB_URL
# Web App URL - Desktop opens this URL for user login (OAuth flow)
# Production example: https://www.multica.ai
MAIN_VITE_WEB_URL=http://localhost:3000
# MAIN_VITE_API_URL
# API URL for main process - Bridged to process.env.MULTICA_API_URL at startup
# so that the externalized @multica/core package can read the correct API URL
# in packaged builds (where .env files are not bundled).
# Production example: https://api.multica.ai
MAIN_VITE_API_URL=http://localhost:8080
# RENDERER_VITE_API_URL
# API URL for renderer process - Used by the React UI for login, user info, etc.
# Production example: https://api.multica.ai
RENDERER_VITE_API_URL=http://localhost:8080
# MULTICA_API_URL
# API URL for core/tools - Used by agent engine tools (web-search, finance)
# Read by core package via process.env.MULTICA_API_URL at runtime
# Production example: https://api.multica.ai
MULTICA_API_URL=http://localhost:8080
# SMC_DATA_DIR
# Root data directory override - Isolates dev data from production.
# When set, all data (sessions, credentials, profiles, app-state, etc.)
# is stored under this directory instead of ~/.super-multica.
# Supports ~ expansion. Set automatically by scripts/dev-local.sh.
# SMC_DATA_DIR=~/.super-multica-dev