multica/apps/desktop/.env.example
Naiyuan Qing ad06679e69 fix: simplify - just say pnpm dev works directly
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-12 19:04:44 +08:00

34 lines
1.4 KiB
Text

# =============================================================================
# Multica Desktop Environment Configuration
# =============================================================================
#
# Local Development:
# Just run `pnpm dev` - connects to dev gateway (multica-dev.copilothub.ai)
# GATEWAY_URL is hardcoded in root package.json, no .env file needed.
#
# Production Build:
# `pnpm build` uses .env.production automatically
#
# Variable naming convention:
# MAIN_VITE_* - Main process only (Node.js, full system access)
# RENDERER_VITE_* - Renderer process only (browser context)
# VITE_* - All processes
#
# =============================================================================
# URL Configuration
# =============================================================================
#
# MAIN_VITE_GATEWAY_URL - WebSocket Gateway
# Hub connects to Gateway for remote device access (QR code pairing)
# Dev: multica-dev.copilothub.ai (hardcoded in root package.json)
# Prod: see .env.production
#
# MAIN_VITE_MULTICA_URL - REST API Server
# HTTP requests for authentication, auto-updates, user data sync
# Dev: not yet used
# Prod: see .env.production
#
# =============================================================================
MAIN_VITE_GATEWAY_URL=http://localhost:3000
MAIN_VITE_MULTICA_URL=http://localhost:3001