.env.example

# Copy this file to `.env` and edit with your own values.
# The dev/ scripts source this file; Vite auto-loads VITE_* variables.

# --- Connection to the remote Linux host running the backend -----------------
# SSH user on the remote host. Must have key-based auth configured (no passwords).
DEPLOY_USER=your-user

# Hostname or IP address of the remote host.
DEPLOY_HOST=192.168.1.100

# Path on the remote host where the project is synced.
# Relative paths (no leading slash) are resolved against the remote user's
# home directory. Use an absolute path like /opt/spark-dashboard if you want
# to sync somewhere else.
# Do NOT use a leading `~/` — that would be expanded to your *local* home.
DEPLOY_DIR=spark-dashboard

# Legacy aliases: SPARK_USER / SPARK_HOST / SPARK_DIR still work as a fallback
# if DEPLOY_* are unset. You'll see a one-line deprecation note at dev.sh startup.

# --- Engine auth (optional) --------------------------------------------------
# Fallback API key sent to every engine endpoint without an explicit
# --engine-api-key. Use this for auth-gated vLLM (started with --api-key) so
# the dashboard's /v1/models lookup succeeds instead of 401-spamming. dev.sh
# forwards this to the remote backend automatically when set.
# SPARK_DASHBOARD_PROVIDER_API_KEY=your-vllm-api-key

# --- Frontend (Vite dev server) ----------------------------------------------
# Where the Vite dev server proxies `/ws` and `/api` calls.
#
# Default `http://localhost:3000` works when you use an SSH tunnel that maps
# the remote host's port 3000 to your local machine
# (e.g. `ssh -L 3000:localhost:3000 ...`).
#
# To connect directly over the network, set this to:
#   VITE_BACKEND_URL=http://${DEPLOY_HOST}:3000
VITE_BACKEND_URL=http://localhost:3000